L0s7 4 Lyf3
Limp Gawd
- Joined
- Mar 3, 2004
- Messages
- 454
Like Drescherjm said, it depends on the developer. Multisocket systems have been around for many years, however because of (mostly) the price it has remained mostly a high end arena for servers and power users (think content creation). So while multithreading applications is nothing new the vast majority of applications were still single threaded. Basically only things like Adobe, film editing, and web/data applications would have the ability to utilize multiple processors. And if you pay attention to benchmarks, content creation apps display the best scaling with # of cores. Games don't display as much, they've only just started to have multithreading (until about 2006-7 99% of games were single) and are still fairly immature implementations of multi-processor support, but it's always getting better.Aaahhh, that makes perfectly sense. Considering how long we have multicore for already, when are the software developers are going to pick up I wonder ?
Do they already classify what PC games have been optimized for 2 or even 4 cores ?
And by the way .... how on earth should I be able to pronounce your screen name, let alone remember it ?
There is a bit of performance overhead just from needing to coordinate multiple processors that won't allow double the cores to mean double the performance. How well the application is multithreaded makes a big difference. The threads won't necessarily have the same workload or be needed simultaneously. There are many, many dynamics to it. But generally more cores is better.
On a single core system things would run like this example:
You'd be encoding a video and trying to browse the web at the same time
The processor has to switch between tasks constantly to try and keep your browsing going smoothly and keep making progress on the encode. Very difficult to keep things running smoothly when encoding can use 100% of your cpu's capacity, and would use more if it could. This switching will make things seem laggy, stuttery, and so on.
While on a dual core the entire encode can be offloaded to processor #2 and can be running 100% cpu usage all day long. Meanwhile cpu #1 is sitting at 15% with whatever you're doing. In terms of user experience you will be running applications just as smoothly as when the single core is not encoding video, but you are doing encoding that video at the same time.
The power of multicore lies in that. You can run demanding applications on separate cores with virtually no effect on the performance of CPU1 (the core that windows is running on) and can do your normal web browsing/word processing and so on just as fast as a single core processor that isn't running those demanding things. So it all relative, the performance increase entirely depends on what you are doing. It's almost impossible to quantify the improvement in user experience of running multiple things at once with no noticeable performance loss. But it sure is nice, that's for sure.