parallel-hashmap/README.md

The Parallel Hashmap: Extremely fast and memory friendly

Click here For a full writeup explaining the design and benefits of the Parallel Hashmap.

IMPORTANT: This repository borrowed a lot of code from the abseil-cpp repository, notably for the implementations of phmap::flat_hash_map, phmap::flat_hash_set, phmap::node_hash_map and phmap::node_hash_set. Please be aware that the code from abseil-cpp has been modified, and may behave differently than the original. This repository should be construed as an independent work, with no guarantees of any kind implied or provided by the authors.

Work in progress - please do not use yet - should be ready before the end of March 2019

This repository aims to provide an set of excellent hash map implementations, with the following charecteristics:

• header only: nothing to build, just copy the parallel_hashmap directory to your project and you are good to go.
• compiler with C++11 support required, C++14 and C++17 APIs are provided
• Very efficient, significantly faster than your compiler's unordered map/set or Boost's, or than sparsepp
• Memory friendly: low memory usage, although higher that sparsepp
• support heterogeneous lookup
• Not yet Tested on Windows (vs2010-2015, g++), linux (g++, clang++) and MacOS (clang++).

Example

#include <iostream>
#include <string>
#include <parallel_hashmap/phmap.h>

using phmap::flat_hash_map;
 
int main()
{
    // Create an unordered_map of three strings (that map to strings)
    flat_hash_map<std::string, std::string> email = 
    {
        { "tom",  "tom@gmail.com"},
        { "jeff", "jk@gmail.com"},
        { "jim",  "jimg@microsoft.com"}
    };
 
    // Iterate and print keys and values 
    for (const auto& n : email) 
        std::cout << n.first << "'s email is: " << n.second << "\n";
 
    // Add a new entry
    email["bill"] = "bg@whatever.com";
 
    // and print it
    std::cout << "bill's email is: " << email["bill"] << "\n";
 
    return 0;
}

Various hash maps and their pros and cons

Key points:

• the flat hash maps may move the keys and values in memory. So if you keep a pointer to something inside a flat hash map, this pointer may become invalid when the map is mutated. The node hash maps don't, and should be used instead if this is a problem.

• the flat hash maps will be smaller, and usually faster than the node hash maps, so use them if you can. A possible exception is when the values inserted in the hash map are large (say more than 100 bytes [needs testing]).

• the parallel hash maps are preferred when you have a few hash maps that will store a very large number of values. The non-parallel hash maps are preferred if you have a large number of hash maps, each storing a relatively small number of values.