Scale

One node to start. More nodes for capacity and for durability.

A node is one machine running the engine. It uses the disks, cores and memory that machine has, and it is licensed as one node whatever those happen to be.

Clustering and replication are licensed per node, and the keys come from us. Start on the free test node, then talk to us about the cluster you need: we size it with you and issue the keys directly.
  • A single node is not durable by itself. Back up anything you cannot lose.
  • Durability comes from more than one node holding your data, not from a setting on one machine, which is what replication across nodes is for.
  • The first node is a free test node, with no time limit, so you can prove it on your own data before you talk to anyone.
  • A node is a node: the licence does not change with its cores, memory or disks.

Today, and what follows

FREE TEST NODE One node your machine, your data free, no time limit: prove it on your data MORE NODES nodenode one engine across nodes, licence key per node REPLICATION dataa secondcopy replication across nodes, for durability
A free test node on one machine, then a licensed cluster running one engine across several nodes, then replication holding a second copy of the data. The keys for the second and third come from us.

How a node is measured

When we measure the engine, we record what the machine was doing while it answered, and publish that beside the number rather than instead of it.

Every disk

Each disk's throughput, against what that disk can physically do, so a number from an idle disk is visible as one.

Every core and thread

How many were actually working, judged over the whole run rather than at its busiest instant.

Every node

The same figures per node and for the cluster together, so one busy machine beside an idle one cannot read as a full one.

A number published without that record is not a result we would ask you to believe. It appears on the benchmark page the same way.

Install the free node Licensing per node