CHOOSE YOUR CATEGORY:

Scaling: 700,000 Simultaneous Connections to VoltDB

One of the original design goals for VoltDB was to support large numbers of connections per server. This kind of came for free with Volt’s event based design. The event based design was driven by a desire to keep the number of active software threads 1:1 with available hardware threads and this basically proscribed any kind of thread per client network IO implementation.… Read more

 

Picture it: Three Nodes, Highly Available Cluster, ~1 Million Transactions/second – with VoltDB

You’ve probably heard about the VoltDB, the super fast distributed ACID SQL RDBMS for OLTP, but you might not be aware of its throughput capabilities in detail. VoltDB achieves its high throughput by eliminating the locking and latching of conventional databases.… Read more

 

877,000 TPS with Erlang and VoltDB

-Edited 5/2/13 by Henning Diedrich to correct configuration typos.

Running on a suitable EC2 configuration (see details below), with our new VoltDB Erlang driver we achieved 877,519 transactions per second.

I am Henning Diedrich [1], CEO of Eonblast Corporation[2] a games company.… Read more

 

686K TPS with Spring Framework Web App and VoltDB

We’ve recently put up a series of blog posts describing the components of a Spring-MVC web application, including VoltDB as the database, that saves votes being called in for talent show contestants.… Read more

 

695k TPS with Node.js and VoltDB

Hi, I’m Henning Diedrich, co-founder and CEO of Eonblast, Inc. I’m a guest contributor to VoltDB’s blog.

In February I was contacted by VoltDB about conducting a benchmarking project.  The company had recently released an updated version of a Node.js client driver that had originally been authored by Jacob Wright, one of VoltDB’s community members. … Read more

 

Is VOLTDB Really as Scalable as they Claim?

Baron Schwartz from Percona has published an analysis of VoltDB’s scaling performance on the MySQL Performance Blog. He has worked with our own Tim Callaghan to apply a mathematical model to the Scalability of VoltDB.… Read more
 

Overclocking Your Database Servers

It seems like I’ve been programming forever (we’re talking TS-1000, TRS-80, and Commodore64). I’ve always been looking to improve the performance of my programs, especially database applications. Better performance can usually be attributed to one of the following:

  • New Hardware[insert name of favorite hardware vendor] has just released new server technology that incorporates improved [RAM | CPU | Disk | RAID Controller].
  • Read more

 

High Availability and Cloudy Problems

VoltDB, like many distributed systems, achieves high availability through redundant processing nodes. VoltDB calls this K-Safety. Essentially, the distributed system can answer any request at at least K+1 servers, so it can tolerate at least K hardware failures.… Read more
 

Key Value Benchmark FAQ

This is a follow up to a previous post on Benchmarking VoltDB against Cassandra on Key-Value-like workloads.
What’s the point of this benchmark?

Point 1: Demonstrate SQL can be fast.… Read more

 

Key-Value Benchmarking

Edit on 6/2/10: Check out the follow up Benchmarking FAQ blog post with links to code.


The NoSQL movement was born of the need to scale data management with predicable cost.… Read more