ekoDB is live. Start building for free
Why ekoDB / Performance
Performance that speaks for itself
Powered by Rust, ekoDB's proprietary database engine is capable of remarkable throughput and sub-ms latency across a variety of workloads. Every figure on this page is read from the benchmark artifact we publish. See for yourself how our performance compares to that of some of the world's top databases.
Benchmarks
Measured against the systems you already run
In industry-standard YCSB benchmarking, ekoDB won 19 of 20 head-to-head matchups against MongoDB, PostgreSQL, MySQL and Redis, by as much as 16.2x. The single exception in this run is read-only against PostgreSQL (0.9x). Throughout, ekoDB is encrypting record bodies, ids, manifests and the WAL at rest, and decrypting on every read, while the compared engines were verified running without encryption at rest.
Relative throughput across the YCSB workloads in this run (average operations per second, higher is better; the fastest engine in each group is set to 100). The ekoDB numbers carry auth, encryption, and search indexing on every operation that the compared engines do not.
Read these as engine throughput, not as what your application will see. Each engine is driven over its own native protocol, and ekoDB's is its internal cluster transport rather than the HTTPS, WebSocket, and SSE endpoints you would connect on. The comparison engines are measured on the protocols their users actually use, so this is favourable to us on that axis.
Documents, JSON, and rows
Durable mode, every database with matching fsync settings.
Key-value
Cache mode, pure throughput, while carrying AES-256-GCM encryption and search indexing that Redis does not provide out of the box. It buys that with cores: Redis saturates one by design, so per unit of CPU it does more work, and ekoDB lands at 0.4x–1.5x of Redis throughput per CPU percent.
Methodology
How these numbers are produced
Document engines are compared in durable mode with matching fsync settings, and key-value in cache mode. Running one engine durable against another buffered is the easiest way to produce a flattering chart, so the run does not do it.
ekoDB is measured with auth, per-operation encryption, and search indexing switched on. The engines it is compared against do not carry those costs in their numbers, so the comparison is unfavourable to us by construction and we publish it that way.
These runs are driven over ekoDB's internal cluster transport rather than the HTTPS, WebSocket, and SSE endpoints an application connects on. Those carry protocol and TLS overhead the harness does not, so treat these as engine throughput rather than as end-to-end numbers for your own client. Measuring the customer transports is tracked and will be published the same way, from the same artifact, once it runs.
Run 0.70.1, 1M records, 64 threads. ekoDB figures include auth, per-operation encryption, and search overhead on every request.
Disclosed with this run:
- ekoDB encrypts at rest; the competitors in this run do not. Read-side results are encrypted-vs-plaintext, not like-for-like
The published artifact this page reads from can be found here. For the full write-up, see the performance reference in the docs.
Go deeper
Explore more about ekoDB
Try ekoDB free
Deploy your first database in minutes. No credit card required.