Google launched it’s Local SSDs for Google Compute Engine and Rajesh Kasanagottu, Google Cloud Solutions Architect and Sunil Sayyaparaju, Aerospike Director of Product & Technology today published a post on the Google Cloud Platform Blog that examined Google’s new Local SSDs and documented RAM-like performance with Aerospike and Local SSDs.
Aerospike certified Local SSDs on Google Compute Engine and showed performance characteristics where 95% of reads completed in under 1 millisecond.
We repeated tests published in the Google blog post – Aerospike Hits 1M Writes/Second on Google Compute Engine with 6x Fewer Servers than Cassandra – using Local SSDs instead of RAM for a 15x storage cost advantage and RAM-like write performance.
Write latencies were similar on Local SSDs and RAM because of write buffering.
Although read latencies are higher with Local SSDs, the differences were not noticeable because most reads using Local SSDs finish under 1 ms and the percentage of reads taking more than 1 ms is similar for both RAM and Local SSDs.
Write throughput was similar on Local SSDs and RAM, but read throughput on Local SSDs was half that with RAM.
At over 500k TPS, read throughput was still very high because Aerospike stores indexes in RAM and data on disk. This number was however affected by the percentage of reads that complete under 1 millisecond, where most reads to SSDs may take between 0.5 to 1 millisecond while reads in RAM are more likely to take less than .5 milliseconds.
Read the full post on the Google Cloud Platform blog.