In comparing my benchmarks with other I have seen on this forum, I find that my read speeds seem similar to others but my write speeds are lower. This has been the case since the first benchmark run, right after setting up the new PC, so I'm guessing it's nothing to do with TRIM. Win 7 64-bit and my driver is msahci.sys, no RAID. Any thoughts as to why the writes are slower than others have reported?
The 80GB SSD has slower Sequential Writes than a 160GB SSD, just keep that in mind when comparing benchmarks. Having said that, your Sequential Write speed is a bit low, should be 80+ MB/s. Try repeating the test and see what happens. Test results do vary, so let's wait for another test and post back what you get.
Your other Write speeds look alright, just a tad bit slower than what I get. I have both 80 and 160GB SSD's
They are faster than mine and my system is fast. I have an AMD 965BE c2, 8 gigs ddr3 ram, MSI 790FX-GD 70 mb with the Intel X25M G2 80gig running my OS -Win7 Pro 64. Your scores are slightly faster. May I suggest that you compare your scores to your old hd and ask is it faster? Wink! What are your computer parts? The scores are very dependant on type of mb, processor etc.
My mb is Asus P7P55D Core i5/i7 carrying 8g DD3 RAM and my processor is Intel Core i7 860 Processor, 2.80GHz Quad Core (overclocked to 3.46GHz for single threaded apps).
I'm guessing that the driver may also effect the speeds. I'm using the msachi.sys driver and I believe that I've read that the Intel drivers are faster. Is this a possible explanation?
It is kind of weird, what you get for Sequential Writes. You should have 80+ for sequesntial write speed. Something is not quite right with your setup, but the problem is finding out what it is. What kind of anti-virus and firewall are you using? Are there any "flags" in Device manager? Any issues shown in SMART with SSD Toolbox? I'm just taking shots in the dark here.
Antivirus: Microsoft Security Essentials
Firewall: Internal Windows Firewall is ON. Only other Firewall is in my router.
No flags in Device Manager.
No issues showing up in SMART or in Diagnostic Scans run in Toolbox.
Do you think it might be interesting to run Optimizer, even though in theory it isn't necessary as I'm using the M/S driver? Is it harmful to use Optimizer to TRIM while windows is doing it automatically?
My PC is new, with a clean Windows 7 install. The guys who built it ran bench tests before they sent it to me and the same slow write speed showed up in those initial results.
So I figured it probably wasn't related to needing to be trimmed. But I've just run the Optimizer and hey, presto! It sure looks like the slow write speed was a TRIM issue. Now I'm going to keep an eye on it to see whether Windows will keep it in shape with auto trim as it's meant to.
I have almost the same setup, P7P55D Pro, 8 GB, i7 860, Win7 64-bit, msahci driver, MS Security Essentials. I was getting the expected performance last time I ran the benchmark.
Have you installed anything else that may have added a filter driver to the storage stack: encryption, or something else you can think of?
If you don't know how to check for Disk Defragmenter, click the Windows icon (first icon on bottom left) and type services local in the Search bar; then click on View local services and scroll to where it says Disk Defragmenter and look to see if it is on Manual, Automatic, or Disabled. If you only use an SSD, then you can set it for Disabled--it should not be running for an SSD.
I have other, non-SSD drives on the system. One of the first things I did was to check the Disk Defrag Schedule. My SSD drive is not available for including in scheduled defrags (as Windows recognises that it is an SSD drive).
Thanks for all the help. I'll report back in 7 to 10 days.
You asked - Is Superfetch disabled?
The service is running. But it was my understanding that it would actually not be active on my SSD drive. I know that Windows has recognised my SSD as it is not available in the Defrag Scheduler. So I have been assuming that it has also stopped Superfetch on the SSD, in spite of its status as running.
Microsoft have said here:
"If the system disk is an SSD, and the SSD performs adequately on random reads and doesn't have glaring performance issues with random writes or flushes, then Superfetch, boot prefetching, application launch prefetching, ReadyBoost and ReadDrive will all be disabled. Initially, we had configured all of these features to be off on all SSDs, but we encountered sizable performance regressions on some systems. In root causing those regressions, we found that some first generation SSDs had severe enough random write and flush problems that ultimately lead to disk reads being blocked for long periods of time. With Superfetch and other prefetching re-enabled, performance on key scenarios was markedly improved."