Slashdot Mirror
A 2nd Core to Keep Windows Chugging Along?
Eh-Wire writes "Almost every hardware junkie I know would give most anything to take a spin in the new dual core hot rods from Dell or one of the custom system builders. But what if you actually needed that second core to run your anti-virus, spyware detection software and firewall just to get a little gaming or Internet surfing done on the first core. Would that really be a good reason to bring home a shiny new machine? I can think of a couple of different things I could use a second core for but running an iron lung on it just to keep the machine chugging along just isn't one of them. Curiously enough, PCMag thinks that's a perfectly good reason."
More power just gives developers an excuse to use more resources. There is no reason a word processing program should lag on a 2+ ghz processor... but there is so much bloat in the program because software vendors feel the need to use up all that extra processing juice that it does...
The example of being able to play games smoothly with anti-virus scanning in the background was just that... an EXAMPLE of a situation where a dual core system might excel. The author mentions a ton of others, like encoding tv input in the background. I think it's rather sensational to say that the author thinks that's the only use or the primary use. The story submitter really needs to get a grip. The article was just trying to make the point that general responsiveness of a dual core system in the face of multiple tasks should be better, and I don't think anyone would disagree with that.
Seriously, what in the world is this article about?
Amazing revelation: dual core processors can do two things at the same time?! You must be kidding me. Any properly threaded application can take advantage of dual cores--there's no need to dream up scenarios where someone could be *gasp* doing multiple things at once.
I don't mean to sound harsh, but I'm confused as to why this is newsworthy.
One Core for me and one Core for all my dead homies.
Actually, I think the PC mag article hits the nail right on the head. The point of of a dual core machine is to run simulanious processes that need to execute side by side.
Now, we all know that most of our processes are input bound, not compute bound. They spend the vast majority of their time waiting for user input. Game are an exception: they both continually process changing data and wait for user input (that's why they are such good benchmarks). Most everything else, however, is input bound. However, many of the processes that run in the background are compute bound, input has little effect on them.
Now in my mind the best way to use a second core is to a) lump all your input bound processes on one core, and your background compute bound processes on the other (like anti-virus, firewall, maybe music, etc.) or b) run compute bound processes on each at the same time (game on one, factor large prime numbers on the other). Either way, there is almost no point in placing seperating the input bound processes between the two cores. This means that unless you are clever about how you divide the work, you aren't going to get much out of it.
...En að Besta Sem Guð Hefur Skapað Er Nýr Dagur
A lot of the systems folks that I've been hearing from and things that I've been reading have suggested that, like it or not, multi-core systems are the way of the future. The argument is that the clock-speed aspect of Moore's law has been slowing down for the past couple of years and that we've seen single processors that are as fast as they'll go with current chip design and fabrication technology. (Barring fundamental breakthroughs, of course.) Hence parallelism and multi-core systems.
I think the point is that it's not really a choice between clock speed and parallelism. You may still have a choice at the moment, but don't expect that to continue. Developers will have to start learning to deal with parallelism if they don't want to fall off the performance curve. I expect we'll start seeing methods, tools, languages and libraries to help developers manage it easily while avoid the common dangers of deadlock and inconsistency. There's some interesting research in the area and we may start seeing some of that find its way into production systems. And of course once developers start adopting parallelism, consumers will in turn begin to see the benefits of it.
In some ways its an obvious message if you look at supercomputers. No one's running serial code on petahertz machines! They're all just systems with large numbers of fairly pedestrian processors with custom fast, low-latency interconnects. As always, this is just the natural trickling down of that to the desktop level.
The 244 watts figure is the power consumption of the entire system, not the chip itself.