Linked by Thom Holwerda on Thu 15th Nov 2007 19:01 UTC, submitted by xpnet.com Research STaff
Benchmarks "'What Intel giveth, Microsoft taketh away'. Such has been the conventional wisdom surrounding the Windows/Intel duopoly since the early days of Windows 95. In practical terms, it means that performance advancements on the hardware side are quickly consumed by the ever-increasing complexity of the Windows/Office code base. Case in point: Microsoft Office 2007 which, when deployed on Windows Vista, consumes over 12x as much memory and nearly 3x as much processing power as the version that graced PCs just 7 short years ago (Office 2000). But despite years of real-world experience with both sides of the duopoly, few organizations have taken the time to directly quantify what my colleagues and I at Intel used to call 'The Great Moore's Law Compensator'. In fact, the hard numbers below represent what is perhaps the first ever attempt to accurately measure the evolution of the Windows/Office platform in terms of real-world hardware system requirements and resource consumption."
Permalink for comment 284852
To read all comments associated with this story, please click here.
RE[3]: My old Pentium 166
by philicorda on Fri 16th Nov 2007 14:34 UTC in reply to "RE[2]: My old Pentium 166"
philicorda
Member since:
2005-12-31

" For example, that P166 couldn't do video encoding/decoding for crap. It could barely handle MP3s, and forget about 3D games."

I beg to differ.
My P166 MMX laptop uses about 5-10% CPU playing back mp3s with Mplayer.
It can also run MDK:
http://en.wikipedia.org/wiki/MDK_(video_game)
at a decent framerate, while doing the 3d rendering entirely in software.

Software is not highly optimised nowadays because programmers no longer need to do so. This is a good thing as it makes code faster to write and more maintainable. It also encourages reusable code rather than tightly written special purpose code.

MULTICS is an example of this. The later *nix clones were simpler and more reliable as they no longer needed all the optimisation and memory sharing tricks required to run a multiuser OS in only 32kB of ram.

Reply Parent Score: 2