there are newer firmwares that fix bugs, so when it's no more stable you should come to the idea "update FW".Įspecially when there was 1.3.3 that adressed serious bugs, 2.x and now even FW-series 5.0x. New driver may changes the way it handles the drive and so it could still address very old problems.ĭude, i can't answer "how comes, everything was fine, didn't changed anything?". Hard to say what exactly is causing the anti-rocksolid-thing you encounter in the FW, since there is no real detailed changelog available. Most of the read speed are faster than the drive physically is capable of, thats why i assumed a ram-cache-software.Īre you sure that your motherboard SATA-Controller driver is properly installed?Ĭertain bugs only may appear in certain situation. but dont worry, should be of no harm yet :):
That 120GB drive wrote approximately 8700 Gigabytes of data, thats 72-times the capacity, so probably some sections of the drive may had 100 write cycles. You have old Firmware, try to update via Corsair Field Updater/Sand-Force Flash Utility, youll find it from the sticky thread regarding your drive's FW in the archive-updates in the FW-Update section.
To restore performance you can try sending TRIM-command via the Toolbox, but i fear TRIM beeing disfunction in your FW-version was a bug. it simply doesnt mean ATTO isn't designed to measure ram-caching. That doesnt mean that your real performance now end up slower than without cache. when it not flushes to disk because it detected the data got deleted and simply delete it from ram then in that moment still the ram needs to process that deletion. the moment it tries to flush gigabytes of bench-junk-data to the disk then slows down. When i run fancy-cache with deferr write enabled all values show up nicely until it reaches a certain chunk size of at least 128, but when i stop it and restart from 128 these values are fine too, the reason a continuus big bench shows slow downs is because you just write big bunches of data and the cache-software on some point has to flush the data to disk. Why did you cancelled ATTO? Please run the full benchmark. I guess you should ask the makers of that cache-software why it shows slowdows on certain chunk size.
Refer to the software-rendor or try read the manual (in case of fancy-cache: everything is very well documented). Your read seem TOO HIGH, so what you are benching is probably not your drive but a bad piece of software laying in the ram.ĪTTO is not designed to bench ram-cache, neither is this corsair able to "help you" as long as this software is running. What do you mean you cleaned the cache? Do you have a third-party Ram-Cache Application running?
0 kommentar(er)
