Anvil's Storage Utilities

[One_Hertz]

ultimate rams

Hey man it's just cache. Totally legit.

[Tiltevros]

Hey man it's just cache. Totally legit.

mine is not cache :/

[Anvil]

X18-M 2R0 4K strip on PCH after SE

Could you check back in this thread for a special build, I'm trying to find out why some are failing on WMI.
Meanwhile could you post the MB, OS, tweaks (if any) and connected drives (all sorts of media)

almost 12.000 points with 4GB test file

Hi Tilt, long time no see
Same goes for you, I need to find out why it fails on WMI on your system as well so could you list just the basics.

Single HDD + fancycache. I think I win.

It's fully legal to use cache, as long as it's mentioned
Not very hard to tell anyways.

I'll display it as part of the info, shouldn't be that hard to detect.

So, what are the most known ones?

[F@32]

Could you check back in this thread for a special build, I'm trying to find out why some are failing on WMI.
Meanwhile could you post the MB, OS, tweaks (if any) and connected drives (all sorts of media)

Here you go. I will get the make and model for HDD and DVDRW later.

ASRock P67 Extreme4 1.90
Core i5 2500K / no OC
G.Skill Ripjaws 1600 4x2Gb / no OC
HD6950 2GB / no OC
Intel Gigabit CT PCIe
M-Audio Delta 2496
Intel x-18M 2x80Gb
Hitachi 2TB SATA2 internal on Marvell
DVDRW SATA2 internal on Marvell
Fantom USB 2TB
Antec Quattro 850W
Antec 1200
Win7 64 bit

So, what are the most known ones?

http://www.superspeed.com/ is another one

[One_Hertz]

mine is not cache :/

Yes, your result is largely cached. Run an 8GB testfile and watch your score drop. The larger the testfile the lesser part of the test is cached.

Anvil - it shouldn't be too hard to detect cache. For example, results over 92ish MB/s in QD1 4KB reads must be cached since nothing can do more than that. If it is not an Iodrive/ACARD then over 40mb/s is not possible unless it is a cached result. You could make the read results cache resistant by creating the test file, then making another 4GB testfile, and then testing the reads on the original testfile. This way the results should be real/represent the actual storage device instead of DRAM.

Or make testfile, ask for a reboot, then test the reads after reboot but that would be annoying as hell.

There isn't an easy way.