Notes on comments.
Welcome to our blog dedicated to the engineering of Microsoft Windows 7
We've talked some about performance in this blog and recently many folks have been blogging and writing about the topic as well. We thought it would be a good time to offer some more behind the scenes views on how we have been working on and thinking about performance because it such an interesting topic for the folks reading this blog. Of course I've been using some pretty low-powered machines lately so performance is top of mind for me as well. But for fun I am writing this on my early holiday present--my new home machine is a 64-bit all-in-one desktop machine with a quad core CPU, discrete graphics, 8GB of memory, and hardware RAID all running a pretty new build of Windows 7 upgraded as soon as I finished the out of box experience. Michael Fortin and I authored this post. --Steven
Our beta isn’t even out the door yet and many are already dusting off their benchmarks and giving them a whirl. As a reminder, we are encouraging folks to hold on benchmarking our pre-production builds. Yet we’ve come to expect it will happen, and we realize it will lead many to conclude one thing or another, and at the same time we appreciate those of you who take the time to remind folks of the pre-ship status of the code. Nevertheless we’re happy that many are seeing good results thus far. We're not yet as happy as we believe we will be when we finish the product as we continue to work on all the fundamental capabilities of Windows 7 as well as all the new features folks are excited about.
Writing about performance in this blog is nearly as tricky as measuring it. As we've seen directional statements are taken further than we might intend and at the same time there are seemingly infinite ways to measure performance and just as many ways to perceive the same data. Ultimately, performance is something each individual feels is right--whether than means adequate or stellar might vary scenario to scenario, individual to individual. Some of the mail we've received has been clear about performance:
You can also see through some of these quotes that performance means something different to different people. As user-interface folks know, perceived performance and actual performance can often be different things. I [Steven] remember when I was writing a portion of the Windows UI for Visual C++ and when I benchmarked against Borland C++ at the time, we were definitely faster (measured by seconds). However the reviews consistently mentioned Borland as being faster and providing feedback in the form of counts of lines compiled flying by. So I coded up a line count display that flashed a lot of numbers at you while compiling (literally flashy so it looked like it couldn't keep up). In clock times it actually consumed a non-zero amount of time so we got "slower" but the reviewers then started giving us credit for being faster. So in this case slower actually got faster.
There's another story from the past that is the flip side of this which is the scrolling speed in Microsoft Word for DOS (and also Excel for Windows--same dynamic). BillG always pushed hard on visible performance in the "early" days and scrolling speed was one of those things that never seemed to be fast enough. Well clever folks worked hard on the problem and subsequently made scrolling too fast--literally to the point that we had to slow it down so you didn't always end up going from page 1 to the end of the document just because you hold down the page down key. It is great to be fast, but sometimes there is "too much speed".
We have seen the feedback about what to turn off or adjust for better performance. In many ways what we're seeing are folks hoping to find the things that cause the performance to be less than they would like. I had an email conversation with someone recently trying to pinpoint the performance issues on a new laptop. Just by talking through it became clear the laptop was pretty "clean" (~40 processes, half the 1GB of RAM free, <5% CPU at idle, etc.) and after a few back and forths it became clear it was the internet connection (dial-up) that was actually the biggest bottleneck in the system. Many encourage us to turn off animations, graphics, or even color as there is a belief that these can be the root of performance. We've talked about the registry, disk space utilization, and even color depth as topics where folks see these as potential performance issues.
It is important to consider that performance is inherently a time/space tradeoff (computer science sense, not science fiction sense), and on laptops there is the added dimension of power consumption (or CPU utilization). Given infinite memory, of course many algorithms would be very different than the ones we use. In finite memory, performance is impacted greatly by the overall working set of a scenario. So in many cases when we talk about performance we are just as much talking about reducing the amount of memory consumed as we are talking about the clock time. Some parts of the OS are much more tunable in terms of the memory they use, which then improves the overall performance of the system (because there is less paging). Other parts of the system are much more about the number of instructions executed (because perhaps every operation goes through that code path). We work a great deal on both!
The reality of measuring and improving performance is one where we are focused at several "levels" in Windows 7: micro-benchmarks, specific scenarios, system tuning. Each of these plays a critical role in how we are engineering Windows 7 and while any single one can be measured it is not the case that one can easily conclude the performance of the system from a measurement.
Micro-benchmarks. Micro-benchmarks are the sort of tests that stress a specific subsystem at extreme levels. Often these are areas of the code that are hard to see the performance of during usage as they go by very fast or account for a small percentage of time during overall execution. So tests are designed to stress part of the system. Many parts of the system are subjected to micro-benchmarking such as the file system, networking, memory management, 2D and 3D graphics, etc. A good example here is the work we do to enable fast file copying. There is a lot of low level code that accounts for a (very significant) number of conditions when copying files around, and that code is most directly executed through XCOPY in a command window (or an API). Of course the majority of copy operations take place through the explorer and along with that comes a progress indicator, cancellable operation, counting up bytes to copy, etc. All of those have some cost with the benefit as well. The goal of micro-benchmarks is to enable us to best understand the best possible case and then compare it to the most usable case. Advanced folks always have access to the command line for more power, control, and flexibility. It is tempting to measure the performance of the system by looking at improvements in micro-benchmarks, but time and time again this proves to be inadequate as routine usage covers a much broader code path and time is spent in many places. For Internet Explorer 8 we did a blog post on performance that went into this type issue relative to script performance. At the other end of the spectrum we definitely understand the performance of micro-benchmarks on some subsystems will be, and should be, carefully measured --the performance of directx graphics is an area that gamers rely on for example. It is worth noting that many micro-benchmarks also depend heavily on a combination of Windows OS, hardware, and specific drivers.
Specific scenarios. Most people experience the performance of a PC through high level actions such as booting, standby/resume, launching common applications. These are topics we have covered in previous posts to some degree. In Engineering Windows 7, each team has focused on a set of specific scenarios that are ones we wanted to make better. This type of the work should be demonstrable without any elaborate setup or additional tools. This work often involves tuning the code path for the number of instructions executed, looking at the data allocated for the common case, or understanding all the OS APIs called (for example registry lookups). One example that comes to mind is the work that we have going on to reduce the time to reinsert a USB device. This is particularly noticeable for UFD (USB flash drives) or memory cards. Windows of course allows the whole subsystem to be plumbed by unique drivers for a specific card reader or UFD, even if most of the time they are the same we still have to account for the variety in the ecosystem. At the start of the project we looked at a full profile of the code executed when inserting a UFD and worked this scenario end-to-end. Then systematically each of the "hot spots" was worked through. Another example along these lines was playback of DVD movies which involves not only the storage subsystem but the graphics subsystem as well. The neat thing about this scenario is that you also want to optimize for the CPU utilization (which you might not even notice while playing back the movie) as that dictates the power consumption.
System tuning. A significant amount of performance work falls under the umbrella of system tuning. To ascertain what work we do in this area we routinely look at the overall performance of the system relative to the same tests on previous builds and previous releases of Windows. We're looking for things that we can do to remove operations that take a lot of time/space/power or things that have "grown" in one of those dimensions. We have build-to-build testing we do to make sure we do not regress and of course every developer is responsible for making sure their area improves as well. We left no stone unturned in terms of investigating opportunities to improve. One of the areas many will notice immediately when looking at the pre-beta or beta of Windows 7 is the memory usage (as measured by task manager, itself a measurement that can be misunderstood) of the desktop window manager. For Windows 7, a substantial amount of architectural work went into reducing the amount of memory consumed by the subsystem. We did this work while also maintaining compatibility with the Windows Vista drivers. We did similar work on the desktop search engine where we reduced not just the memory footprint, but the I/O footprint as well. One the most complex areas to work on was the improvements in the taskbar and start menu. These improvements involved substantial work on critical sections ("blocking" areas of the code), registry I/O, as well as overall code paths. The goal of this work is to make sure these UI elements are always available and feel snappy.
It is worth noting that there are broad based measures of performance as well that drive the user interface of a selection of applications. These too have their place--they are best used to compare different underlying hardware or drivers with the same version of Windows. The reason for this is that automation itself is often version dependent and because automation happens in a less than natural manner, there can be a tendency to measure these variances rather than any actual perceptible performance changes. The classic example is the code path for drawing a menu drop down--adding some instructions that might make the menu more accessible or more appealing would be impossible to perceive by a human, but an automated system that drives the menu at super human speed would see a change in "performance". In this type of situation the effect of a micro-benchmark is magnified in a manner inconsistent with actual usage patterns. This is just a word of caution on how to consider such measurements.
Given this focus across different types of measurement it is important to understand that the overall goal we have for Windows 7 is for you to experience a system that is as good as you expect it to be. The perception of performance is just as important as specific benchmarks and so we have to look to a broad set of tools as above to make sure we are operating with a complete picture of performance.
In addition to these broad strategies there are some specific tools we've put in place. One of these tools, PerfTrack, takes the role of data to the next level with regard to performance and so will play a significant role in the beta. In addition, it is worth reminding folks about the broad set of efforts that go into engineering for performance:
Perftrack is a very flexible, low overhead, dynamically configurable telemetry system. For key scenarios throughout Windows 7, there exist “Start” and “Stop” events that bracket the scenario. Scenarios can be pretty much anything; including common things like opening a file, browsing to a web page, opening the control panel, searching for a document, or booting the computer. Again, there are over 500 instrumented scenarios in Windows 7 for Beta.
Obviously, the time between the Stop and Start events is meant to represent the responsiveness of the scenario and clearly we’re using our telemetry infrastructure to send these metrics back to us for analysis. Perftrack’s uniqueness comes not just from what it measure but from the ability to go beyond just observing the occurrence of problematic response times. Perftrack allows us to “dial up” requests for more information, in the form of traces.
Let’s consider the distribution below and, for fun, let's pretend the scenario is opening XYZ. For this scenario, the feature team chose to set some goals for responsiveness. With their chosen goals, green depicts times they considered acceptable, yellow represents times they deemed marginal, and red denotes the poor times. The times are in milliseconds and shown along the X axis. The Hit Count is shown on the Y axis.
As can be seen, there are many instances where this scenario took more than 5 seconds to complete. With this kind of a distribution, the performance team would recommend that we “dial up” a request for 100+ traces from systems that have experienced a lengthy open in the past. In our “dialed up” request, we would set a “threshold” time that we thought was interesting. Additionally, we we may opt to filter on machines with a certain amount of RAM, a certain class of processor, the presence of specific driver, or any number of other things. Clients meeting the criteria would then, upon hitting the “Start” event, configure and enable tracing quickly and potentially send back to us if the “Stop” event occurred after our specified “threshold” of time.
As you might imagine, a good deal of engineering work went into making this end to end telemetry and feedback system work. Teams all across the Windows division have contributed to make this system a reality and I can assure you we’ll never approach performance the same now that we have these capabilities.
As a result of focusing on traces and fixing the very real issue revealed by them, we’ve seen significant improvements in actual responsiveness and have received numerous accolades on Windows 7. Additionally, I’d like to point out that these traces have served to further confirm what we’ve long believed t be the case.
This post provides an overview of the ways we have thought about performance with some specifics about how we measure it throughout the engineering of Windows 7. We believe that throughout the beta we will continue to have great telemetry to help make sure we are achieving our goals and that people perceive Windows 7 to perform well relative to their expectations.
We know many folks will continue to use stop watches, micro-benchmarks, or to drive automated tests. These each have their place in your own analysis and also in our engineering. We thought given all the interest we would talk more about how we measure things and how we're engineering the product.
--Steven and Michael
@Fredledingue -- I think it is fair to leave a little room for differing views. Some people do prefer a richer user-interaction and it does feel more responsive to them because it is interactive. Looking at sports on tv these days shows that just having boring white overlay for scores is not as interesting to a mass audience even if some feel it is "tiring on the eyes".
Again, I am not saying anyone is right or wrong but just that there are many perspectives that are equally valid.
Just note, for the sake of discussion, that percieved lack of performance rarely takes the shape of something unexpectedly disapearing from the screen, but instead of something slow to go, leaving a residual shape or not going away at all.
Also the intent of reducing a window is to see what is behind it. When we hit the reduce button, our brain expect to see, for example, the desktop. The animation just make it longer to deliver the brain satisfaction of seeing this desktop.
I wonder how many users are realy aware that this is an intended visual effect and not a naturaly slow process... Would be interresting to conduct a study about that (one day your team has nothing to do -lol-)
Maybe for some it's cool because they have time to think about something else in the meantime, I don;t know... ;)
I've seen significant strides in performance efforts but I have a question. Does Microsoft have a valid reason why the typical Microsoft OS slows down over time? I believe that I hear this comment too often for it to be considered perceived performance but I may be wrong. Any technical insight into this matter would be great or maybe you've been working on it in this revision? Thanks much!
Private Beta is OUT!!!
Beta Pubblic is coming??!!
@Stevex "In my opinion the need to re-pave a machine every year or two to regain performance is Windows's biggest drawback."
Yes, I agree!
But the way w7 will be distributed (with Media Player, with outlook, with IE etc) is also a big drawback!
Distribution is a discussion I very much miss!
I have been testing 6801 since the PDC, it works above my expectations in most areas, I am using it on a 10 year old laptop and it is actually more snappy & responsive than XP sp3.
I am wondering one thing where are the Beta Invitations that were promised...I have not received one yet!
This is Private Beta , no pubblic beta.
prior to deploying something audiences need a test
"Anyone is welcome to send me the before and after taskmgr listings for 6801 and I will be more than happy to learn from them (I can't promise a full support/diagnosis if I get a lot of these)."
How can we send you these files?
Steven: fair enough, I can understand non power users actually like this setting. Just make sure this can always be turned off for us experienced users :) This is actually the only Performance Settings window setting that I turn off; I find the rest of them very useful. Maybe your team can tweak it some more for it to be less intrusive while still achieving it's goal.
Also, something not related to performance: I dislike that the bread crumbs bar in Windows Vista does not always show to top most folder (i.e. Computer) when browsing for example the Documents folder. I find the arrows between the breadcrumbs very hard to use (easy to miss, not easy to switch to folders). If I can always navigate to the top most 'folder' (i.e. Computer) with one click, I can easily navigate to the folder I want.
"I've seen significant strides in performance efforts but I have a question. Does Microsoft have a valid reason why the typical Microsoft OS slows down over time? I believe that I hear this comment too often for it to be considered perceived performance but I may be wrong. Any technical insight into this matter would be great or maybe you've been working on it in this revision? Thanks much! "
I think that Steven and DavidFie answered your question above: To quote David: "These factors include Malware, poorly behaved drivers or services, and some Windows issues which we've addressed in Win7 as well as some which we’re still working on.
The PerfTrack telemetry will help us understand more about this area to improve both Windows and the ecosystem much like the Windows Error Reporting system has improved application and systems crashes and hangs over the last several years."
Vista not slows down over time!
probably all depends on user
I wonder if all this data could be actively compiled into a public database that matched a change to the system to the affect it had on performance or reliability.
I guess W7 would submit the information back to MS similar to the way it reports crash reports. As end-users' data populated the system, it might be a good tool to refer to before installing a driver, or enabling a feature.
It would be something like a wiki, except your PC does the contribution in the background.
You could see how similar systems were affected by installing a new graphics driver or disabling visual affects.
Over time, it would probably be very useful in isolating shoddy software and illustrating its negative impact.
I have posted this before, but there are a lot of people out there that like the visual effects. Even if they are cool for a short time. I see all time from people, "why doesn't Microsoft have customizable visuals like compiz, or better minimize effects like Genie in OS X" I for one, would like to see something like this, or at least an expansion pack or something. I'm the type of person that customizes everything. Just to be different.
Also, multiple desktops would be a nice feature too. Very useful for work. I'm a system administrator and use Dameware, pcanywhere, RDP, HP and SUN ILO's, and would be nice to have these on different desktops. I know that there are 3rd party software, but these are not always stable.
The reason Windows slows down over time seems to be (from my experience) software like iTunes, RealPlayer, QuickTime, Skype, etc all needlessly loading themselves at startup. In many cases it's simply for brand awareness (why, oh why do you need a QuickTime icon in the system tray? Why doesn't Apple feel that Mac users need an icon on their menu bar? Oh of course, they're not in the business of making Windows nice to use now, are they?)
If you're careful you can avoid installing this stuff, and find Windows is fast for years.
I usually happen to find these in my friends PC
Start - Msconfig
Apple update (real Virus install crapware like Mobile me,Safari+more problem etc)PS. Zune in Europe PLS!!!
Adobe Update (reader-flesh etc)
Office or Open Office
and more more software :D