AS-SSD Incompressible Sequential Performance

The AS-SSD sequential benchmark uses incompressible data for all of its transfers. The result is a pretty big reduction in sequential write speed on SandForce based controllers.

Incompressible Sequential Read Performance - AS-SSD

Incompressible Sequential Write Performance - AS-SSD

AS-SSD performance is pretty impressive as well. We see a huge advantage over a single Vertex 3.

Sequential Performance vs. Transfer Size (ATTO) Final Words
Comments Locked

38 Comments

View All Comments

  • GullLars - Thursday, June 30, 2011 - link

    This card will get decimated by even an 80GB ioDrive, not to mention the 320GB ioDrive Duo, in just about any real world scenario. They are designed from completely different standpoints.

    While both are highly parallell, the ioDrive is highly optimized for latency and can push close to 20.000 4KB random read IOPS (~75-80MB/s) at a QD of 1, while Revodrive 3 x2 reaches 13K at QD 3, and around 4-5K at QD 1.
    The ioDrive also handles mixed IO well, and scales really fast at low block sizes and queue depths, so you would need incredibly heavy parallell workloads to keep it at a notable QD (>10).

    What bothers me the most with the Revodrive 3 x2 is that it doesn't implement an onboard cache at all. With 64-512MB you could use it for read-ahead and hit those GB/s+ seq bandwidth numbers at a QD of 1 for fairly small block sizes.
    With a (super?)capacitor you could also safely use say 8-16MB of that cache for write buffering and saturate the array.
  • GullLars - Thursday, June 30, 2011 - link

    Correction, RevoDrive 3 x2 benched 7K 4KB random read IOPS @ QD 1 in AS SSD.
  • Jharne - Tuesday, June 28, 2011 - link

    The INF mentions VEN_11AB & VEN_1B4B which are both Marvell. So I'm guessing they built the controller.
  • DigitalFreak - Tuesday, June 28, 2011 - link

    LOL. All the trouble they go through to hide the controller vendor and all you need to do is look at the vendor ID
  • VStrom - Tuesday, June 28, 2011 - link

    You can boot with this on x64 with an unsigned driver...you just need to load Windows with the signed driver validation disabled (F8 before Windows loads).
  • DanNeely - Tuesday, June 28, 2011 - link

    If you need to do this before every boot it's a non-option in the server world. In normal operation no keyboard/mouse/monitor will be attached, all interaction will be via remote desktop type services after it's booted.
  • VStrom - Tuesday, June 28, 2011 - link

    True, but I was referring to Andand's comment specifically about Win 7 saying "Windows 7 x64 won't boot off of the RevoDrive 3". When this ships, the driver will be ready and a non-issue for servers.
  • bacomatic - Tuesday, September 13, 2011 - link

    Apparently this has been fixed, I am booting Win 7 x64 from this drive with the current drivers.
  • quiksilvr - Tuesday, June 28, 2011 - link

    I would have figured with this strong staple in the 2.5" SSD market with TRIM enabled devices this would not be hard to to.
  • mikeblas - Tuesday, June 28, 2011 - link

    Comparing this device against consumer-level SSDs seems like a waste of time. Why not compare against fusionio?

    I'd also like to see a benchmark that runs for a sustained period. The problem with SSD is the ability to keep up with write loads. If you run the 4K random IO benchmark for 48 hours, does the IOPS rate spike or trend downwards, or does it stay flat? The write ratio of your benchmark is around 33%, which I don't think represents OLTP applications too well.

    The review doesn't comment on the stability of the drivers, their memory usage on the host, or the management and monitoring tools for the drive. Do I get a tool that measures remaps, does SNMP, or email alerting?

Log in

Don't have an account? Sign up now