Brian Bulkowski, Aerospike Founder and CTO Blog, Business

Aerospike is an unusual database. It’s fast, it takes less CPU and DRAM, and it pushes storage harder. That’s how it achieves multi-million transaction per second per server rates, with sub-millisecond access times.

This speed makes Aerospike the database of choice for fraud detection, machine learning-based behavioral recommendations, advertising optimization, and a host of other uses. In general, Aerospike can be used as a front-edge database store for applications who need terabytes of data. We’ve recently seen many cases where data science shows that moving to a Hybrid Memory database with the advantages of Flash economics while achieving the needed performance for these use cases make a lot of sense.

IBM cloud has two unique advantages: it’s driven by “bare metal cloud” capabilities which can operate in parallel to standard virtualized machines.

No virtual machine migration with IBM Cloud

IBM cloud virtual machines don’t undergo “behind the scenes” virtual machine migration. Those migrations are what often lead to unexpected “server restarts” in some clouds – which cause loss of all data persisted “locally”. In those clouds, Aerospike will heal the cluster by continually migrating data.

In most public clouds, local drives must be considered “ephemeral”, not persistent. Unlike IBM’s cloud, where you can allocate database servers that are truly reserved, and fail only when the underlying hardware fails. While Aerospike’s “shadow drive” configuration can be used to continually push writes to the slower persistent storage ( as in EBS in Amazon’s cloud ), this extra complexity costs latency, performance, and money.

This impact simply doesn’t happen in IBM’s bare metal cloud.

Expanded hardware choices

IBM gives you the ultimate for your hardware choices. The IBM cloud allows choosing a specific amount of DRAM and specific storage options. You can purchase DRAM values from 32GB to 6TB, with 4 different Flash drive models, which can be mixed and matched in different quantities.

Aerospike consumes exactly 64 bytes per object in the database, and can push a storage device far harder than any other database. There is less write amplification, and fewer writes, due to Aerospike’s unique Hybrid Memory architecture.

Which hardware choice is best for you will depend on your use case. By consulting with Aerospike’s solutions architects, we can recommend a hardware configuration which results in optimal cloud spend, and the lowest possible latency.

The following measurement numbers were achieved using YCSB on IBM bare metal instances, and show the performance of the IBM cloud.

 

Instance Type

Client Transactions/s

95th Percentile (ms)

99th Percentile (ms)

Object Size (bytes)

Object Count

Disk Size

Xeon E3 1270v3 1Gpbs

130,000

3.4

5.5

500

240,000,000

1.2TB

Xeon E3 1270v3 1Gbps

30,000

3.0

4.6

3000

240,000,000

1.2TB

2x Xeon E5 2620v4 10Gbps

222,000

1.7

3.2

500

240,000,000

1.2TB

2x Xeon E5 2620v4 10Gbps

100,000

2.6

3.4

3000

240,000,000

1.2TB

 

We invite you to read this IBM white paper, “Powering high-performance applications with Aerospike on IBM Cloud”.

About Author

mm

Brian Bulkowski, Aerospike Founder and CTO

All posts by this author
Brian is a Founder and the CTO of Aerospike. With almost 30 years in Silicon Valley, his motivation for starting Aerospike was the confluence of what he saw as the rapidly advancing flash storage technology with lower costs that weren’t being fully leveraged by database systems as well as the scaling limitations of sharded MySQL systems and the need for a new distributed database. He was able to see these needs as both a Lead Engineer at Novell and Chief Architect at Cable Solutions at Liberate - where he built a high-performance, embedded networking stack and high scale broadcast server infrastructure.