Testing Performance on a Texas Memory System RAMSAN-500 pt3

This is part 3 in my RAMSan Series.

While I am confident the read-only test was a reasonably good test ( I just needed to push more ), my mixed load test was marred by issues.  It was really a quick attempt to get a heavy read/write workload.  I ran into issues with how I wrote this so I will spare you the details.  Some flash devices are notoriously poor performing in writes, so its important to at least briefly look at this.  What I will share are the IOPS & latency numbers from this test.  The mixed workload does updates & selects at this point, these are a mix of PK updates, secondary index updates, etc.  These typically are built to run faster and smaller the the read-only IO bound workload.

By the 11th interval the Ramsan was pretty much complete.  The peaks are whats interesting…  lets look at this in a slightly different way.

So in the admittedly flawed mixed workload I am hitting upwards of 4x the iops.  Once again I can not help but think this is really being helped by the extra DRAM…

And finally in the mixed test lets look at the latency #’s from the disk.

Once again the RAMSan shows some spectacular response time numbers form a fairly decent sized load.

I feel I could have pushed the device a lot then I did, but the tests that were done far exceed what most San’s could handle.  The RAMSan 500 is one of the fastest devices I have tested so far.  Its price tag (removed this because my previous info was incorrect ) makes this definitely a solution for large customers for customers in the high end market, but if you need really fast disk performance this is a device you definitely want to take a look at.

This entry was posted in benchmark, hardware, linux, Matt, mysql, performance, raid. Bookmark the permalink.

Comments are closed.