gDown Performance

Same graph, same queries and the same machine for every database of the table above: the figures below are the median over the rounds of the set-up table, measured on arm64.

Durability of the databases measured

For these performance figures, every database is measured in persistent mode (data written to disk, replayed on restart).

Databases measured

DatabaseVersion measuredEdition or licenceProtocolMeasurements
gDownmain @ ac35131, 2026-10-23JVM build, benchmark settingsBoltworkloads
Neo4j5.26.31 communityCommunity (GPLv3)Boltworkloads
Memgraph3.13.1Community (BSL 1.1)Boltworkloads
FalkorDB6.0.2 on Redis 8.10.2SSPL 1.0RESPworkloads
ArcadeDB26.10.1Apache 2.0Boltworkloads
TuGraph4.5.1Community (Apache 2.0)Boltworkloads
Apache AGE1.8.0 on PostgreSQL 18.6 (Debian 18.6-1.pgdg13+2)Apache 2.0 (PostgreSQL extension)JDBCworkloads

How the benchmark runs

PropertyValue
Architecturearm64
MachineApple M4 Max, 16 logical CPUs, 64 GB RAM; Docker 29.9.2
Container limits4 CPUs, 8 GB of memory per container
Graph of the workloads100,000 nodes, 1,000,000 relationships, generated with a fixed seed
Rounds3 full rounds; every figure is the median of the rounds
ClientsOne Java client on the host; 1, 4, 8 concurrent clients depending on the workload
ProtocolThe transport of each database (table above): Bolt on both sides for gDown and Neo4j; a warm-up round before each workload, not counted
Dates2026-10-24 – 2026-10-24

Startup, memory, CPU and size

Without index

WorkloadgDownNeo4jMemgraphFalkorDBArcadeDBTuGraphApache AGE
Startup to the first answer0.84.00.60.21.50.50.9
CPU average (100 % = one core)100180234100102104109
CPU peak274385408161207404244
Peak memory8994,8055424266,415381476
Data on disk17683638939120173529

With indexes on the identifiers

WorkloadgDownNeo4jMemgraphFalkorDBArcadeDBTuGraphApache AGE
Startup to the first answer0.84.00.60.21.50.50.9
CPU average (100 % = one core)10517922499102104109
CPU peak279385410160207404244
Peak memory8234,8075064296,415381476
Data on disk18183738939120173529

Startup: from docker run to the first answer to RETURN 1, median of several attempts, measured once and shown in both configurations; the other rows cover the whole run of the workloads. CPU and disk are not ranked: a database that writes nothing durable has 0 MB on disk.

Complex reads: median latency — LDBC SNB Interactive

The 29 queries of the LDBC Social Network Benchmark Interactive workload (14 complex reads, 7 short reads, 8 updates; Apache 2.0, unchanged) all run on a generated graph with the SNB schema.

  • 29 / 29 queries run: 14 complex reads, 7 short reads, 8 updates
  • 3 / 3 members of a 3-node cluster return the same row counts for the 21 reads
  • 18 ms median write while the leader takes 1,365 acknowledged writes (3,000 persons)
  • 0 ms median read on a follower during those writes (95th percentile: 30 ms)

All databases, 3,000 persons

WorkloadgDownNeo4jMemgraphFalkorDBArcadeDBTuGraphApache AGE
complex-12.97.4––10.0––
complex-21.12.41.6211.92.3––
complex-311.39.810.3–17.7––
complex-40.91.90.70.61.9–131.5
complex-57.59.54.02.215966.5––
complex-63.35.32.1–8.7––
complex-70.72.00.7––––
complex-80.61.50.70.51.3––
complex-95.26.016.2–16.5––
complex-101.04.9–––––
complex-110.92.20.90.52.8––
complex-121.42.54.0–2.7––
complex-130.51.6––0.7––
complex-141.02.0––2002.9––

A dash: the database refuses the query, exceeds its timeout, or returns a different number of rows than Neo4j (its time would mean nothing). Case by case:

All databases, 30,000 persons

  • complex-1 : gDown 12.9 ms, Neo4j 51.5 ms
  • complex-2 : gDown 2.8 ms, Neo4j 2 ms
  • complex-3 : gDown 15.1 ms, Neo4j 13.3 ms
  • complex-4 : gDown 1.6 ms, Neo4j 1.7 ms
  • complex-5 : gDown 19.5 ms, Neo4j 16.9 ms
  • complex-6 : gDown 6.7 ms, Neo4j 7 ms
  • complex-7 : gDown 1.4 ms, Neo4j 1.4 ms
  • complex-8 : gDown 0.8 ms, Neo4j 1 ms
  • complex-9 : gDown 15.1 ms, Neo4j 8.5 ms
  • complex-10 : gDown 4.4 ms, Neo4j 4.2 ms
  • complex-11 : gDown 1.9 ms, Neo4j 1.8 ms
  • complex-12 : gDown 2 ms, Neo4j 2.4 ms
  • complex-13 : gDown 0.9 ms, Neo4j 1 ms
  • complex-14 : gDown 4 ms, Neo4j 3.3 ms

Median over 5 persons after a warm-up round, one run per database, in containers limited as in the set-up table; every database is reached over its own transport (Bolt on both sides for gDown and Neo4j: the round trip is counted on both sides). “< 1 ms” means that the median rounds to zero milliseconds. Short reads: median under 1 ms for gDown (0.5 to 0.7 ms) against 0.7 to 1 ms for Neo4j, same protocol on both sides.

At 3,000 persons (90,000 nodes and 470,000 relationships, loaded through Raft in 16 s), medians stay under 60 ms. Two optimisations found by this test: complex-1 went from 0.6 s to 34 ms, complex-14 from 2 s to 8 ms.

Not official LDBC results: these figures are derived from the LDBC SNB Interactive workload and have not been audited by the LDBC (Linked Data Benchmark Council). The data is generated by the test, not by the LDBC Datagen: the times are not comparable with published LDBC results. One run per configuration. The test also found two defects, now fixed.

Source: gluonify-gdown, README and the reports of LdbcSnbTest and LdbcClusterTest.

Cypher coverage (the openCypher TCK on every base) is on the comparison page.

Latency and throughput, workload by workload

Same graph, same queries and the same machine for every database of the table above: the figures below are the median over the rounds of the set-up table, measured on arm64.

Latency is the median (p50) in milliseconds, lower is better; the workloads with several clients are in requests per second, higher is better. The best value of each row is in bold. Nothing is tuned beyond the defaults of each image; gDown runs on the JVM with a 6 GB heap and a 2 GB page cache, Neo4j with a 4 GB heap and a 2 GB page cache. Each run starts from a fresh container, loads the graph in UNWIND batches, checks that the databases agree on the results, then measures.

Without index

WorkloadgDownNeo4jMemgraphFalkorDBArcadeDBTuGraphApache AGE
Read by id0.300.720.290.160.350.460.23
Read by property3.368.226.902.440.330.440.24
Range on a property (100 values)3.1410.711.63.2024.175.80.24
Count a label0.350.613.860.180.4198.28.59
1 hop0.280.510.280.170.330.500.27
2 distinct hops0.330.560.300.200.400.600.72
3 distinct hops0.841.140.470.341.051.385.63
Group by + top 103.279.8831.115.78.6514561.4
Filter + aggregate4.0611.39.723.565.5277.724.2
Count a pattern (all KNOWS between persons)15.721259.131.410083746.2
Hot reads + a full traversal per 1000.260.550.310.170.390.500.29
First 10 rows of a large result0.280.580.370.200.570.530.19
Write: 1 node per request0.400.550.420.340.510.450.25
Writes while a long scan runs0.490.540.4835.10.600.480.27
8 clients: 1 hop16,3138,4388,86329,15610,8844,72316,715
4 clients: writes6,5685,2423,5244,8513,4523,6189,302

ArcadeDB (indexed) is always measured with an index: its internal identifiers rule out the lookup by id() used for the other columns. Its column is here so that nothing is missing, but its ratios without index compare an index with a scan: see the table with indexes for the like-for-like comparison.

With indexes on the identifiers

WorkloadgDownNeo4jMemgraphFalkorDBArcadeDBTuGraphApache AGE
Read by id0.290.720.290.160.350.460.23
Read by property0.270.500.270.180.330.440.24
Range on a property (100 values)0.300.480.290.1824.175.80.24
Count a label0.260.473.640.150.4198.28.59
1 hop0.260.460.270.160.330.500.27
2 distinct hops0.310.510.290.180.400.600.72
3 distinct hops0.760.990.440.311.051.385.63
Group by + top 103.289.5231.915.08.6514561.4
Filter + aggregate4.0515.49.733.535.5277.724.2
Count a pattern (all KNOWS between persons)15.720961.631.410083746.2
Hot reads + a full traversal per 1000.260.530.310.170.390.500.29
First 10 rows of a large result0.270.560.320.200.570.530.19
Write: 1 node per request0.390.570.430.320.510.450.25
Writes while a long scan runs0.500.540.4935.00.600.480.27
8 clients: 1 hop16,3658,4278,94028,98810,8844,72316,715
4 clients: writes6,5305,0893,5445,1123,4523,6189,302

Loading the graph

Without index

WorkloadgDownNeo4jMemgraphFalkorDBArcadeDBTuGraphApache AGE
Load time7.98.73.35.114.4102.398.9
Loading rate138,434126,238328,444214,62376,13710,74911,118

With indexes on the identifiers

WorkloadgDownNeo4jMemgraphFalkorDBArcadeDBTuGraphApache AGE
Load time10.210.94.640.414.4102.398.9
Loading rate108,100100,503239,10727,24276,13710,74911,118

What to take from it

  • FalkorDB is the fastest on short operations (reads by id, hops, single-node writes) and on throughput with several clients, with the shortest client path (RESP). Look at “writes while a long scan runs”: its writes wait behind a long read; it writes nothing durable by default and its loading with indexes is the slowest.
  • gDown is faster than Neo4j on most workloads (geometric mean below 1 in both configurations), loads faster and keeps its data in far less disk space. It is level or slower on the first rows of a large result and on single-node writes: see First 10 rows and Write: 1 node.
  • Against Memgraph, gDown wins on grouping, label counts and throughput with 8 clients, and loses on short reads, hops and writes. Memgraph does not force its commits to disk each time, unlike gDown and Neo4j.
  • ArcadeDB, always measured with an index, is competitive on reads but slow on ranges and on writes with several clients.
  • Memory: the databases that keep everything in RAM (Memgraph, FalkorDB) use the least. gDown and Neo4j run here with generous heaps, and gDown needs far less with a smaller heap for the same latencies (see the native measure above).

What this comparison does not say

  • Durability differs: gDown and Neo4j sync to disk at each commit; Memgraph only every 100,000 transactions; FalkorDB writes nothing durable by default; the settings of the other databases were not checked. The write lines therefore do not compare the same guarantee.
  • The databases that speak Bolt share the same Java driver; FalkorDB is measured with a minimal RESP client written for the benchmark, which shortens its path on reads (see the transport column).
  • ArcadeDB is always measured with an index, in both tables (its internal identifiers rule out the lookup by id()); a database without a value in a configuration was not measured in it.
  • The graph fits in memory for all of them. A graph larger than RAM, replication, failover, vector search, graph algorithms and reads during concurrent writes are not measured. One node of each database.
  • ArcadeDB runs with an unbounded heap: its memory figure is not comparable. Its image is a development snapshot.
  • A machine that was not idle, a few rounds: count on ±10 % on every cell.

Source: gluonify-gdown, the raw results of each round (docs/bench) and scripts/bench-compare.py, assembled by a script of this site; the benchmark script is in the same repository.