Hi there!
What should the benchmarks for a Dual-2.7 GHz G5 be? My benchmarks improved a lot after installing the alpha 5.2 worker, but they're still only half of what the top Powe…
Quote:
Originally Posted by TiloProbst
those Top Macs are Quad CPU, so they should score way higher then your Dual machine
I was talking about the PowerMac7,3, not about t…
Quote:
Originally Posted by phantomac
I was talking about the PowerMac7,3, not about the PowerMac11,2, which is the 4 CPU machine.
A dual 2.7 GHz G5 should still be the second …
I was quite dissapointed of dual 2.7ghz performance.
http://setiathome.berkeley.edu/show_...hostid=1789945
My DC 2.3ghz's outperforms that easily.
http://setiathome.berkeley.edu/sh…
Interesting...
Your 2.7 gets about what my 2.5 does. Actually, a little worse in some cases.
It should do a bit better but....what kind of ram?
My 2.5 has PC3200-30330 ram…
Don't expect any of these machines to scale linearly in performance with clock speed. The determining factor here is definitely L2 cache and memory bandwidth, although the clock sp…
What I notice most of all is that there seems to be large variation
even between machines of the same type.
I ponder whether some G5 chips work better than others for
reasons of…
hello,
i replaced my ipods battery the other night and let it charge overnight. the next morning i went to listen to it, selected the song and hit play. before it would actually pl…
Hi,
Let's say I have the following:
code:
NSProgressIndicator* progress; (assume it's initialized and visible etc)
for (int i = 0; i < 5; ++i) {
[progress setDoubleValue: …
When you update the value of a progress indicator, it's marked as needing display the next time through the runloop (with setNeedsDisplay: YES). Your code, however, never returns …
Quote:
Originally Posted by smeger
When you update the value of a progress indicator, it's marked as needing display the next time through the runloop (with setNeedsDisplay: YES…
He already said that, for some reason, an NSTimer is really impractical for what he's doing. I'd think that indicates a problem with the program's structure, but y'know, whatever. …
Thanks for the responses. I was hoping to avoid pthreads as it's a bit overkill. As for some people who are unhappy with my design I can elaborate as to why it's uncomfortable to…
I don't think that would work. If I declared the array on the stack and then passed it into the user info of the timer wouldn't it already be popped off the stack by the time the …
Yeah, it would be off the stack; that's why I suggested an NSDictionary. Actually, the userInfo object is declared to be an id, so it should be an Objective-C object, anyway (it's …