Tags

  • AWS (7)
  • Apigee (3)
  • ArchLinux (5)
  • Array (6)
  • Backtracking (6)
  • BinarySearch (6)
  • C++ (19)
  • CI&CD (3)
  • Calculus (2)
  • DesignPattern (43)
  • DisasterRecovery (1)
  • Docker (8)
  • DynamicProgramming (20)
  • FileSystem (11)
  • Frontend (2)
  • FunctionalProgramming (1)
  • GCP (1)
  • Gentoo (6)
  • Git (15)
  • Golang (1)
  • Graph (10)
  • GraphQL (1)
  • Hardware (1)
  • Hash (1)
  • Kafka (1)
  • LinkedList (13)
  • Linux (27)
  • Lodash (2)
  • MacOS (3)
  • Makefile (1)
  • Map (5)
  • MathHistory (1)
  • MySQL (21)
  • Neovim (10)
  • Network (66)
  • Nginx (6)
  • Node.js (33)
  • OpenGL (6)
  • PriorityQueue (1)
  • ProgrammingLanguage (9)
  • Python (10)
  • RealAnalysis (20)
  • Recursion (3)
  • Redis (1)
  • RegularExpression (1)
  • Ruby (19)
  • SQLite (1)
  • Sentry (3)
  • Set (4)
  • Shell (3)
  • SoftwareEngineering (12)
  • Sorting (2)
  • Stack (4)
  • String (2)
  • SystemDesign (13)
  • Terraform (2)
  • Tree (24)
  • Trie (2)
  • TwoPointers (16)
  • TypeScript (3)
  • Ubuntu (4)
  • Home

    C++ map vs unordered_map

    Published Jul 29, 2019 [  C++  ]

    std::map

    • ordering: increasing order (by default)
    • implementation: self balancing tree like Red-Black Tree
    • search time: log(n)
    • insertion time: log(n) + rebalance
    • deletion time: log(n) + rebalance

    Use std::map when

    • You need ordered data
    • You would have to print/access the data (in sorted order)
    • you need predecessor/successor of elements

    std::unordered_map

    • ordering: no ordering
    • implementation: hash table
    • search time: O(1) -> average O(n) -> worst case
    • insertion time: same as search
    • deletion time: same as search

    Use std::unordered_map when

    • You need to keep count of some data (Example - strings) and no ordering is required.
    • You need single element access i.e. no traversal.

    References: https://www.geeksforgeeks.org/map-vs-unordered_map-c/