Why doesn't Google just run Dijkstra faster?
Dijkstra explores radially from the origin, expanding into every nearby neighbourhood before reaching the destination. Speeding up individual steps doesn't help—it still touches millions of irrelevant nodes. Contraction Hierarchies works by structurally skipping them, not computing faster.
Answered in
Why Google Maps Computes Shortcuts OfflineContraction Hierarchies precomputes shortcut edges offline so routing queries skip neighbourhood streets and touch only 2,000 nodes in under 10 milliseconds.
Read the full analysisOther questions this article answers
More system design questions
- What is a shortcut edge and when is it precomputed?
- How much space do shortcut edges take compared to the original graph?
- Can Contraction Hierarchies handle dynamic graphs like traffic or road closure?
- Why contract low-degree nodes first instead of high-degree ones?
- What is a CRDT and why does it matter for real-time collaboration?
- How do CRDTs handle concurrent edits without a central server referee?
- Why did Figma move from operational transforms to CRDTs?
- What's the memory and bandwidth cost of running replicas locally?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the System Design beat.