Benchmarks
Every performance number on this site, with the graph it ran on, the hardware as far as it was recorded, the commit that published it and the command that reproduces it.
Graph kernels on the GPU
The same kernels on the CPU and on the GPU, with identical results (PageRank bit for bit).
Kernels in query plans
The planner replaces multi-hop aggregates, filtered aggregates and Top-N with kernels over the adjacency export. CPU only.
Graph algorithms
The algo.* procedures on the CPU.
| PageRank (20 iterations) | 104 ms |
|---|---|
| Weakly connected components | 52 ms |
| Triangle count | 184 ms |
Adjacency export
Building the compressed adjacency that kernels and algorithms read. It is built once per committed state and shared.
| From the in-memory store | 0.26 s |
|---|---|
| From the disk-resident store | 0.6 s |
| Size of the export | 32 MiB |
Bulk import
graphbuff import writes store records directly, without Cypher or a redo log, compared with loading the same files through LOAD CSV and CREATE.
How to read these
The numbers are the engine's own measurements, copied from its README. They are single runs on one developer machine, not an independent benchmark, and nothing here compares GraphBuff with another database. Where the hardware was not written down, this page says so. Keeping results in the repository is an open item in the engine's progress log.