Re: Upgraded to XP here
Thanks for the reply. However, it's not only only SQL Servers 2005 and upwards.
For example, I have a little VBA application which runs in Excel. It creates a linked list and in the run that I hae now the list is about a quarter of a million nodes in length.
I've written the code so that the speed of writing to the list is optimised, i.e. pointers where there should be to get new nodes in the shortest amount of time.
Each node is about 1.5k in size and, as I say, there's about a quarter of a million of them.
Run the same code with the same data on a new W7 machine and the other on a crufty XP box and the timings are interesting -- the XP box is almost exactly three times faster to run up and down the linked lists than the W7 machine.
I use linked lists because the Collection class is far, far too slow to contemplate for serious amounts of data bashing.
I make a pile of five dimensional linked lists and run up and down them all the time in my analysis and guess which machines it runs faster on? Yes, the old XP boxes. On any of my W7 machines it's just too slow to use.
But for most folk who like to look at pictures of internet cats, Skype long lost relatives in far off lands and such then W7 is fine. But if I want to really hammer data day in and day out then W7 just doesn't cut it.
I've got friends in the music business and they can't bear to run their recording studio (no, not mp3 dance 'music' but proper recording) on W7; give them XP and they're happier.
I know of many a developer who have upgraded their machines from W7 to XP simply because XP runs better than W7.