Originally posted by benixau
hey - NEWSFLASH - under OS X the app doesn't need to be multi-processor aware to benfit from having two of those things.
Is it just me or this sentence sounds very rude?
Under _any_ smp aware OS you'll see some benefit by having a second CPU, whether the application in question is SMP aware or not. An OS is always doing several things at once, and the app would have one cpu to itself, while the OS could use the other for its things. But the benefit will, in most cases, be quite insignificant (depending on the app, os, etc)
It works like this, say whil you are playing DoomIII:
Proc 1: window server .....
Proc 2: Doom III
this way you get an entire proc (or the better part of it) just for the app. It makes life easy.
Unless I am very mistaken, if you compare the CPU requirements for doom, and that of the window server, you'll see the Doom CPU at 100%, and the other hovering at around 5% or 10%. This is just my guess. I can't actually test it, but I would be surprised if the window server required so much CPU power.
Yes, all games will see a small improvement by having a second CPU, because that second CPU can take care of things like managing the network trafic, window server, etc, but all that work should be minimal compared with that of playing the game. So the improvement will be minimal, and probably not worth the money. Money that would be better spent on a better video card, or a beer or 10.
Also all multi-threaded apps can have OS X divide the task between the procs and then return it.
I'm not sure if you are confusing multi-threading with multi-processing here. I don't know what your background and knowledge is of this, so I'm sorry if I offend you. But those two things are two different concepts.
Can OSX really asign each thread to a CPU? how does it do this without spawning a new process? please, enlighten me if you know the answer.
Cheers
Latino