← Back to home
Comparison · DevOps

GraphHopper vs Slurm

A side-by-side editorial comparison of GraphHopper and Slurm — release velocity, themes, recent moves, and the top alternatives to consider.

GraphHopper vs Slurm: at a glance

FeatureGraphHopperSlurm
SectorDevOpsDevOps
Velocity score0.05.0
Sparks · 30d00
Top themesrouting, openstreetmap, custom-models, navigationhpc, job-scheduling, reliability, tls
Last editorial update2h ago2h ago
WebsiteVisit →Visit →

What is GraphHopper?

GraphHopper finished moving vehicle profiles into custom models, then went back to OSM tags.

GraphHopper ships a major roughly every six months, with 11.0 in October 2025 the most recent. The architectural work happened in 9.0, which moved vehicle encoded values into the custom model, removed the built-in vehicle parsers' name property and the wheelchair parsers, allowed external encoded values in custom models, and blocked built-in custom model filenames. 10.0 then spent itself on storage layout — byte-based edge storage, a Map-based KVStorage API, wider georef fields — and 11.0 is almost entirely OSM tag interpretation: maxspeed=none handling, separate foot and bike road access, cycleway oneway combinations, toll parsing moved into a country-aware parser.

Read the full GraphHopper trajectory →

What is Slurm?

Slurm 26.05 makes SLUID the default job identity and pulls TLS into the daemons.

Slurm is maintaining three branches concurrently — 26.05 as the new major line, 25.11 as the stable one, and 25.05 still receiving fixes — and releases them in same-minute pairs. The 26.05 line introduces SLUID as the default identifier used in cgroup paths and step lookups, and a tls/s2n path with a certgen plugin for generating step certificates. Everything else in this window is correctness work: controller crashes under load, shutdown and reconfigure races, memory leaks in slurmstepd and slurmrestd, and cross-version compatibility between mismatched daemons.

Read the full Slurm trajectory →

GraphHopper vs Slurm: editorial side-by-side

G0.0

GraphHopper finished moving vehicle profiles into custom models, then went back to OSM tags.

◆ Current state

GraphHopper ships a major roughly every six months, with 11.0 in October 2025 the most recent. The architectural work happened in 9.0, which moved vehicle encoded values into the custom model, removed the built-in vehicle parsers' name property and the wheelchair parsers, allowed external encoded values in custom models, and blocked built-in custom model filenames. 10.0 then spent itself on storage layout — byte-based edge storage, a Map-based KVStorage API, wider georef fields — and 11.0 is almost entirely OSM tag interpretation: maxspeed=none handling, separate foot and bike road access, cycleway oneway combinations, toll parsing moved into a country-aware parser.

◆ Where it's heading

The configuration model is settled and the effort has moved to routing quality. Nearly every change in 11.0 is about reading OSM tags more faithfully for a specific mode — bicycle handling on living streets, foot instructions at junctions, MTB speeds on compacted surfaces, HGV tolls by country — which is the long tail of work that separates a routing engine that runs from one people trust. Turn restrictions are the recurring source of real bugs, appearing across 9.0, 10.0, 10.1 and 11.0 with via-way handling repeatedly needing correction. The new POST /navigate endpoint accepting a GraphHopper request is the one API-surface addition in this window.

◆ Prediction

Expect continued profile-level tuning driven by OSM tagging edge cases rather than architectural change, since three consecutive majors have narrowed in that direction. Turn restriction handling with multiple or overlapping via-ways is the most likely source of the next bugfix release, given its record across every version here.

S
Slurm
DEVOPS
5.0

Slurm 26.05 makes SLUID the default job identity and pulls TLS into the daemons.

◆ Current state

Slurm is maintaining three branches concurrently — 26.05 as the new major line, 25.11 as the stable one, and 25.05 still receiving fixes — and releases them in same-minute pairs. The 26.05 line introduces SLUID as the default identifier used in cgroup paths and step lookups, and a tls/s2n path with a certgen plugin for generating step certificates. Everything else in this window is correctness work: controller crashes under load, shutdown and reconfigure races, memory leaks in slurmstepd and slurmrestd, and cross-version compatibility between mismatched daemons.

◆ Where it's heading

The bulk of the engineering effort visible here goes to concurrency and lifecycle correctness in slurmctld — races between the purge thread and job/node write locks, accounting_storage callers racing plugin teardown, connection plugin initialization ordering, forwarding threads outliving shutdown. That is the profile of a codebase being hardened for larger and busier clusters rather than one adding scheduling features. The second thread is upgrade tolerance: multiple fixes exist purely to keep a 26.05 slurmd working with a 24.11 sattach or a 25.05 slurmstepd, which tells you how staged real site upgrades are.

◆ Prediction

Expect 26.05.x to keep issuing fixes for the SLUID transition and for mixed-version daemon combinations, since both are where this window's regressions cluster. The 25.05 line looks close to the end of its fix stream, with its recent releases limited to shutdown races and build compatibility.

Alternatives to GraphHopper and Slurm

Other DevOps products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either GraphHopper or Slurm.

See all GraphHopper alternatives → · See all Slurm alternatives →

Recent activity from GraphHopper and Slurm

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 25d agoSlurm26.05.2 adds a cgroup path escape hatch back to job IDs
  2. 25d agoSlurm25.11.7 fixes requeued jobs losing their license reservations
  3. 2mo agoSlurm26.05.1 repairs mixed-version and post-upgrade job handling
  4. 2mo agoSlurmSlurm 26.05 ships SLUID identity and an in-tree TLS path
  5. 2mo agoSlurm25.11.6 clears reconfigure and shutdown hangs in slurmctld
  6. 2mo agoSlurm25.05.8 rejects nobody-user submissions and fixes shutdown races
  7. 9mo agoGraphHopper11.0 refines mode-specific OSM tag handling and adds POST /navigate
  8. 1y agoGraphHopper10.2 fixes an import failure on recent OSM turn restriction data
  9. 1y agoGraphHopper10.1 cherry-picks a via-way turn restriction fix
  10. 1y agoGraphHopper10.0 reworks edge storage layout and turn cost computation
  11. 2y agoGraphHopper9.1 is a bugfix release with no documented changes
  12. 2y agoGraphHopperVehicle profiles collapse into custom models in GraphHopper 9

Frequently asked questions

What is the difference between GraphHopper and Slurm?

They serve adjacent needs but don't currently overlap on shipped themes. Slurm is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is GraphHopper better than Slurm?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Slurm is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.

What are the best alternatives to GraphHopper?

Top GraphHopper alternatives in DevOps are ranked by recent ship velocity. Browse the "GraphHopper alternatives" section above for the current picks, or visit /alternatives/graphhopper for the full list with editorial commentary on each.

What are the best alternatives to Slurm?

Top Slurm alternatives in DevOps are ranked by recent ship velocity. Browse the "Slurm alternatives" section above for the current picks, or visit /alternatives/slurm for the full list with editorial commentary on each.