Benchmarks

How fast is TripleTrail?

We measure TripleTrail against other open-source engines on public benchmark suites and on spatial and routing work. The harness and the raw results are in the source repository, so you can run them yourself.

Where TripleTrail leads

General SPARQL on the BSBM explore and update workloads, spatial joins on real OpenStreetMap data, routing, combined route and spatial queries, and bulk loading.

Where others lead

PostGIS answers simple box and nearest-neighbour lookups in under a millisecond. maplib is faster on BSBM business-intelligence queries and on the RINF Sparqloscope set. QLever stores data in less disk space.

How we measured

One Hetzner ccx43 server (16 dedicated vCPU, 64 GB RAM), November 2026. Each engine ran alone, with its result cache off, using its own fastest correct form of each query.

Berlin SPARQL Benchmark (BSBM)

The classic benchmark for SPARQL stores: an e-commerce dataset with three workloads. Explore is a mix of typical lookups, BI is heavy analytical queries, update mixes writes in. Query mixes per hour, higher is better.

WorkloadTripleTrailOxigraphmaplibQLeverJena TDB2
Explore, 1 M triples69,04233,19128,981*2,904*5,389
Explore, 10 M triples112,30714,76616,482*5,379*1,630
BI, 1 M triples17,76835035,228†8,5061,716
BI, 10 M triples4,757478,571†3,477190
Update, 1 M triples40,80426,0212,517*n/a4,001
Update, 10 M triples60,86915,093206*n/a1,640

* Skipped the DESCRIBE and CONSTRUCT queries (2 of 12), because the BSBM test driver asks for RDF/XML, which these endpoints do not serve. † maplib 0.20.26 skipped BI query 5 and returned wrong result counts on queries 7 and 8. QLever has no update workload result. 1 M and 10 M triples are BSBM scales 2,785 and 28,480 products.

Sparqloscope: one query per SPARQL feature

Sparqloscope, from the QLever team at the University of Freiburg, generates about 100 queries that each test one SPARQL feature: joins, OPTIONAL, MINUS, property paths, regular expressions and more. Geometric mean per query, lower is better.

DatasetTripleTrailmaplibQLeverOxigraphJena TDB2
BSBM, 1 M triples3.2 ms5.1 ms5.8 ms60.1 ms81.7 ms
RINF, European rail infrastructure register13.7 ms7.1 ms30.7 ms182.9 ms206.2 ms

TripleTrail, maplib, QLever and Jena answered all 102 queries; Oxigraph timed out on one.

Spatial and routing

Our own benchmark for spatial networks: a synthetic rail network of 10.5 million triples modelled on RINF, and real OpenStreetMap data for Norway. PostGIS with GiST indexes and pgRouting is the reference. Warm median time, lower is better.

QuestionTripleTrailPostGIS / pgRoutingQLeverJena GeoSPARQL
Everything in a box / polygon3.5 / 2.1 ms0.3 / 0.2 ms729 / 552 ms32 / 50 ms
Everything within a distance2.0 ms1.7 ms135 ms29 ms
10 nearest signals5.3 ms0.3 ms135 ms3.01 s
Join: signals within 20 m of track elements1.12 s851 ms2.77 stimeout (300 s)
Join, OSM Norway: stations × admin units218 ms312 ms5.86 s6.86 s
Join, OSM Norway: tracks × land use519 ms1.30 s4.23 stimeout (600 s)
Join, OSM Norway: tracks within 5 m of tracks309 ms5.08 s1.46 s155 s
Track length per region1.93 s4.94 sn/an/a
Kilometre post → point on the track4.5 ms9.5 msn/an/a
Shortest route (Dijkstra)40 ms1.04 sn/an/a
Shortest route, contraction hierarchies5.1 msn/an/an/a
Route with constraints31 ms922 msn/an/a
Five shortest routes93 ms21.3 sn/an/a
100 × 100 travel cost matrix647 ms24.7 sn/an/a
Route, then signals within 50 m of it766 ms1.07 sn/an/a
Load 10.5 M triples and build indexes6.5 s29.8 s9.9 s150.5 s
Size on disk746 MiB893 MiB204 MiB1.94 GiB

n/a: the engine has no such function. pgRouting rebuilds its graph from SQL on every call, which is most of its time on point-to-point routes; TripleTrail keeps named networks in memory. The first spatial query after a restart builds TripleTrail's spatial index (125 ms for the box selection), and the first route builds the network (about 5 s); the full results list every cold time.

Method and fairness

  • All engines ran on the same server, one at a time, with the same data. PostGIS reads the same geometries as the RDF engines.
  • Every engine uses its own fastest correct query form; results are checked against each other, and wrong answers are reported, not counted as fast.
  • Versions: PostgreSQL 16, PostGIS 3.4, pgRouting 3.6, Apache Jena Fuseki GeoSPARQL 6.2 (TDB2), QLever (November 2026 image), maplib 0.20.26, Oxigraph (latest release at the time of the run).
  • Every suite, query and raw result is in the bench/ folder of the source repository, with a one-command run on your own machine or on a rented server.
  • Benchmarks are a guide, not a promise. Your data and queries decide. Send us a sample and we will measure it.