Posted 07/02/08 at 02:49:47 PM by Paul Lilly
Let's set aside Crysis, heavy encoding, and the few other specialized tasks capable of making a high end rig writher in agony. For everything else, we're at a point where the software needs to catch up with the hardware, and that hasn't always been the case. Remember when your anti-virus program would kick in, preventing you from being able to open a Word document or perform other mundane tasks with any sense of urgency? Neither Intel's brute-force, gazillion stage pipeline nor AMD's Rainman approach to efficiency were enough to get over the performance hump, and it took the advent of mulitple core processors to blow the doors open to multitasking.
Now that dual- and quad-core processors are mainstream parts, the roles have been reversed. There exists only a handful of programs developed to intelligently utilize additional cores, and even less that take advantage of the additional computing power effectively. Toss benchmarking by the wayside and you probably won'tt be able to discern between a dual-core E8200 (2.66GHz) system, and one equipped with a quad-core Q9450 (2.66GHz). For that to change, developers must learn how to program for not only today's hardware. but tomorrow's too.
Find out what 'unwelcome advice' Intel has for developers after the jump.
Feature
Review
Feature
Feature
Feature
