Quote:
Originally Posted by KnifeMissile
But that's my point... In the example of the "flop out" user you describe above, they would see no improvement in performance, whether they use a dual core system or not. The fact that you think they would exemplifies my point. People don't understand how programs work or what the second core buys them.
|
"Flop out" meaning to go somewhere else and get work done because that app is taking too long. Sure they would see an improvement, unless the test were designed to prevent it.
Knife, I'm a bit baffled by your contention. The XP thread scheduler is neurotic and wasteful but it will show an increase in work with multiple cores and multiple single-threaded applications. NT has had parallelism built into the kernel since way back when. XP Home will see some less benefit due to its further restrained scheduling support vs. multi-core + HT. But the benefit is there to experience.
Try setting affinity (for a few more % benefit) with task mgr or one of many launch utils. Monopolize each core with separate tasks and time vs. disabling one core completely. I don't know how you interpret the increase in work as other than an increase in performance. Not only is it measurable, but it's obvious to users making rigorous use of multiple single-threaded apps. XP's scheduler is less efficient than tuned, multi-threaded apps, and it's possible to sabotage the benefit with I/O or common resource blocks, (including user input) but otherwise independent apps do eat this stuff up.
I did have a customer a bit ago who was disappointed with his dual-core laptop. He hadn't patched XP power management for multi-core use and it would never load up either processor. That thing was a dog. Now I couldn't pry it from his cold dead fingers.