638
edits
Changes
→Results
DenseTable and OpenTable must initialize the entire table each time they resize. CloseTable also allocates large chunks of memory, but like a <code>vector</code>, it does not need to write to that memory until there is data that needs to be stored there.
This means that for a huge Map with no delete operations, a Close table could use more virtual memory but less physical memory than its open addressing counterparts. This will not be the only use case that stresses memory usage, though. Applications may also create many small tables and may delete entries from large tables.
[[Image:jorendorff-dht-InsertSmallTest-speed.png]]
