|
I've been working/running on a Intel Core 2 Quad since earlier last year as my main machine, i've noticed the difference as I tend to run several large different programs at a time. At the moment i've got 2 virtual Pc's running, 2 instances of Visual Studio 2005 with large solutions, general standard stuff and its flying along merrily.
Even though these programs are not multithreaded, it means they can run simultaniously which is great as im running a test app on my main pc, which is calling the two virtual servers and delivering instantanious response.
In terms of developing for multiple cores, the problems come when you have to target a range of users, how much would you like it for example if I released a new version of Call of Duty and said you had to have a Quad core processor to run it?
It is a balancing act, the game engine im currently working on will use multithreading across multiple core's (graphics run on one, game logic another, in game communication on another) however I do rely on Windows to distribute these tasks across the different cores efficiently.
Threading has always been a difficult thing to do with Windows, even when the .Net Framework came out it was a nightmare, Microsoft's behavour is to drop/destroy a thread at the first error rather then allowing you the chance to debug it. I spent months bulletproofing a single task.
__________________
Chris
.Net C# ASP.NET Developer
Windows Systems Administrator
|