The most recent one is Engineering Windows 7 Graphics Performance which I thought might be of interest to you guys. It's much more high-level than most people here as games and graphics developers will be used to, but provides some interesting context nonetheless.
The above diagram/section caught my attention. Seems that after some experimentation they found that the single threaded and globally locking nature of GDI was a huge bottleneck in the responsiveness of the system.
Firstly this raised an interesting example for me as my team are working on profiling/benchmarking a complex enterprise IT system at the moment. The above finding on the E7 blog demonstrates that getting cold, hard data can throw up problems or characteristics you never even thought existed!
Secondly, this is of interest because my NUMBER ONE biggest irritation with Windows is when its unresponsive. I simply won't tolerate it and expect that if I click on something that it should respond immediately - maybe not with the full results, but at least a progress bar, loading image or something similar - a locked up application is absolutely and unequivocally unacceptable.
Anyway. Seems that if they solved that bottleneck then the lock-ups disappeared:
There are a few other interesting bits and pieces in the blog entry along similar lines, but thats the one that really stood out for me.
Anyone here using the Win7 RC yet?
In other news... Extremely busy at the moment, and any spare time I've got is being directed towards 'side projects', namely D3D11 tessellation, my SO debugging article and taking a look at SlimDX11. Not much spare time for forums unfortunately.
Oh, and I'm getting a new bike - so more time outdoors and less time behind a PC [cool]