Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
5.9, the WD 640KS was the lowest score, im surprised it was that low considering most consider it the best 7200RPM drive
5.9, the WD 640KS was the lowest score, im surprised it was that low considering most consider it the best 7200RPM drive
5.9, the WD 640KS was the lowest score, im surprised it was that low considering most consider it the best 7200RPM drive
IIRC, and I don't know if this changed in 7, but the Vista version of this test only took into account the HDD the OS is on's size, not any of its speed characteristics. Am I mistaken?
With respect to disk scores, as discussed in our recent post on Windows Performance, weve been developing a comprehensive performance feedback loop for quite some time. With that loop, weve been able to capture thousands of detailed traces covering periods of time where the computers current user indicated an application, or Windows, was experiencing severe responsiveness problems. In analyzing these traces we saw a connection to disk I/O and we often found typical 4KB disk reads to take longer than expected, much, much longer in fact (10x to 30x). Instead of taking 10s of milliseconds to complete, wed often find sequences where individual disk reads took many hundreds of milliseconds to finish. When sequences of these accumulate, higher level application responsiveness can suffer dramatically.
With the problem recognized, we synthesized many of the I/O sequences and undertook a large study on many, many disk drives, including solid state drives. While we did find a good number of drives to be excellent, we unfortunately also found many to have significant challenges under this type of load, which based on telemetry is rather common. In particular, we found the first generation of solid state drives to be broadly challenged when confronted with these commonly seen client I/O sequences.
An example problematic sequence consists of a series of sequential and random I/Os intermixed with one or more flushes. During these sequences, many of the random writes complete in unrealistically short periods of time (say 500 microseconds). Very short I/O completion times indicate caching; the actual work of moving the bits to spinning media, or to flash cells, is postponed. After a period of returning success very quickly, a backlog of deferred work is built up. What happens next is different from drive to drive. Some drives continue to consistently respond to reads as expected, no matter the earlier issued and postponed writes/flushes, which yields good performance and no perceived problems for the person using the PC. Some drives, however, reads are often held off for very lengthy periods as the drives apparently attempt to clear their backlog of work and this results in a perceived blocking state or almost a locked system. To validate this, on some systems, we replaced poor performing disks with known good disks and observed dramatically improved performance. In a few cases, updating the drives firmware was sufficient to very noticeably improve responsiveness.
To reflect this real world learning, in the Windows 7 Beta code, we have capped scores for drives which appear to exhibit the problematic behavior (during the scoring) and are using our feedback system to send back information to us to further evaluate these results. Scores of 1.9, 2.0, 2.9 and 3.0 for the system disk are possible because of our current capping rules. Internally, we feel confident in the beta disk assessment and these caps based on the data we have observed so far. Of course, we expect to learn from data coming from the broader beta population and from feedback and conversations we have with drive manufacturers.
For those obtaining low disk scores but are otherwise satisfied with the performance, we arent recommending any action (Of course the WEI is not a tool to recommend hardware changes of any kind). It is entirely possible that the sequence of I/Os being issued for your common workload and applications isnt encountering the issues we are noting. As weve said, the WEI is a metric but only you can apply that metric to your computing needs.
MY HDD score did not change while all other scores did (from Vista), so I would guess no, it has not changed.IIRC, and I don't know if this changed in 7, but the Vista version of this test only took into account the HDD the OS is on's size, not any of its speed characteristics. Am I mistaken?
5.9 due to my 150GB WD Raptor ..
@ tissimo
your graphic score 6.5 is low for your gtx260 SSC ???, mine is 7.2 with all stock.
I am running with Win 7 build 7229 x64 Bit and use Nvidia driver 185.85 whql.
phatbx133
I7 Rig in my sig running at 200x2