Benchmarks · By the Numbers, OpenCypher
The Linked Data Benchmark Council publishes the standard test for graph databases, the LDBC Social Network Benchmark: 21 queries over a simulated social network of people, posts and friendships. We ran it on TETRAbase and on Neo4j, the leading graph database, with the same data on the same server. TETRAbase answered all 21 queries 66 times faster on 177 million connections.
We also tested writes, and queries and writes running together. Neo4j won some of those tests, and the charts below mark each one.
66x
Faster than Neo4j
Time to run all 21 queries on 177 million edges (SF10)
13x
Less CPU
Processor time used by the same 21 queries
10.3x
More queries per second
Eight clients querying at once, on 17 million edges (SF1)
7.9x
Less disk space
Data on disk after the write tests. TETRAbase encrypts its data; Neo4j did not
2.1x
Less memory
Peak memory while running the 21 queries on 177 million edges
1.78B
Edges queried in less time than Neo4j takes on 17 million
TETRAbase on the largest dataset against Neo4j on the smallest
We tested TETRAbase once, on 1 November 2026. We tested Neo4j Community 5.26 on the same server in September and October. TETRAbase used no indexes and kept its data encrypted on disk.
01 · Speed at every size
LDBC publishes its data in standard sizes called scale factors. SF1 holds 17 million edges, the connections between people, posts and places; SF100 holds 1.78 billion. TETRAbase ran 29.5 times faster than Neo4j at SF1 and 66 times faster at SF10. We tested Neo4j up to SF10. TETRAbase went on to SF100 and answered all 21 queries in 11.3 seconds, less time than Neo4j took at SF1.
66.0x faster
Time for all 21 queries
13.0x less CPU
Processor time
2.1x less memory
Peak memory
02 · Query by query
The 21 queries range from short lookups, such as a person's profile, to long searches through friends of friends. TETRAbase gained most on the long searches: it answered IC9, which finds recent posts by friends and friends of friends, 423 times faster. Neo4j answered one query faster at every size: IC7, which finds who recently liked a person's posts.
Each bar divides Neo4j's median time by TETRAbase's, on a log scale. Teal bars mark the queries TETRAbase answered faster; the grey bar marks the one Neo4j answered faster. Select a query to compare both times.
03 · Writes
Both databases take writes in openCypher, the graph query language. We tested 18 kinds of write: creating records and connections, updating them, upserting (inserting or updating) and deleting. Each test wrote one row at a time, 1,000 rows from a list, or a range of 1,000 rows, first with 1 client and then with 32 clients at once. After every test we read each row back to confirm the database saved it. Neo4j created records in bulk and overwrote ranges of records far faster than TETRAbase.
Each bar divides TETRAbase's rows written per second by Neo4j's, on a log scale, with 200,000 rows loaded. Grey bars mark the writes Neo4j did faster. ✗ marks the test where three Neo4j writes failed with deadlocks.
04 · Reads and writes together
Real applications read and write at the same time. We ran 8 clients repeating the 21 queries alongside 1, 4 or 16 clients writing, for 60 seconds each. TETRAbase answered 10.3 times as many queries as Neo4j with no writers, and 3.9 times as many with 16. Neo4j wrote about three times as much data in every test, and its queries slowed less when the writers started.
8 readers, no writers
8 readers and 1 writer
Queries took longer than with no writers: TETRAbase +113.1%, Neo4j +5.4%
8 readers and 4 writers
Queries took longer than with no writers: TETRAbase +147.9%, Neo4j +2.2%
8 readers and 16 writers
Queries took longer than with no writers: TETRAbase +177.2%, Neo4j +7.8%
8 readers, after the writers stopped
Queries took longer than with no writers: TETRAbase +13.0%, Neo4j +0.0%
Each figure counts complete runs of the 21 queries per second, across all 8 readers. Neither database returned a wrong answer: we checked 24,000 answers from TETRAbase and 3,750 from Neo4j.
05 · DataPower
5 systems. Same data. Same operations. 2 CPU cores, 8 GB of memory.
How DataPower works, with all 15 test runs →Measurements from Nov. 1, 2026. See the specs.
520
DataPower at 3 million data elements
Quick test profile, one run per database
06 · How we tested
Both databases ran the same queries on the same data. Their setups differed in five ways, and three of those differences favoured Neo4j.
| TETRAbase | Neo4j 5.26 | Favours | |
|---|---|---|---|
| Queries and inputs | Same | Same | Neither |
| Indexes for the queries | None | 9 constraints and 8 indexes, the LDBC reference setup | Neo4j |
| Constraints for the writes | 6 unique | 6 unique | Neither |
| Saving writes to disk | Saves every write before confirming it, and saves writes that arrive together in one step | Saves its transaction log on every write | Neither |
| Encryption on disk | Always on | Off | Neo4j |
| Memory settings | Defaults | Tuned for each dataset size | Neo4j |
| Server and clients | Same machine | Same machine | Neither |
| Test date | 1 November 2026 | 24 September 2026 for queries, 26 October 2026 for writes | Neither |
We share the raw results, Neo4j's stored results, the query inputs and the test harness on request.
Download the full report, 36 pages (PDF) ↓A standard benchmark runs on someone else's data. Bring your own workload, and we'll compare TETRAbase with your current system.