public member function
<unordered_map>

std::unordered_multimap::reserve

void reserve( size_type n );
Request a capacity change
Sets the number of buckets in the container (bucket_count) to the most appropriate to contain at least n elements.

If n is greater than the current bucket_count multiplied by the max_load_factor, the container's bucket_count is increased and a rehash is forced.

If n is lower than that, the function may have no effect.

Parameters

n
The number of elements requested as minimum capacity.
Member type size_type is an unsigned integral type

Return value

none

Example

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
// unordered_multimap::reserve
#include <iostream>
#include <string>
#include <unordered_map>

int main ()
{

  std::unordered_multimap<std::string,std::string> myumm;

  myumm.reserve(7);

  myumm.insert({{"apple","NY"},{"apple","WA"},{"peach","GA"}});
  myumm.insert({{"orange","FL"},{"cherry","UT"}});
  myumm.insert({{"strawberry","LA"},{"strawberry","NC"}});

  for (auto& x: myumm) {
    std::cout << x.first << ": " << x.second << std::endl;
  }

  return 0;
}

Possible output:
strawberry: LA
strawberry: NC
cherry: UT
orange: FL
apple: NY
apple: WA
peach: GA


By calling reserve with the size we expected for the unordered_multimap container we avoided the multiple rehashes that the increases in container size could have produced and optimized the size of the hash table.

Complexity

In case of rehash,
Average case: linear in container size.
Worst case: quadratic in container size.

Iterator validity

If a rehash happens, all iterators are invalidated, but references and pointers to individual elements remain valid.
If no actual rehash happens, no changes.

See also