| Code-Review | +1 |
thanks, it does look like this marginally improves performance (https://pprof.corp.google.com/?id=93c69790661d3a31eca4f8a09dfdcce4&id0=832c3aac6ab1e13307e50b912eec892f&filter=showfrom:%255Ev8%253A%253Ainternal%253A%253Amaglev%253A%253A,focus:operator%255C%255B%255C%255D&tab=flame)
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
lgtm
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Replace `std::unordered_map` with `absl::flat_hash_map`.
The Chromium containers guide
(https://chromium.googlesource.com/chromium/src/+/HEAD/base/containers/README.md)
recommends using `absl::flat_hash_map` as a default map choice instead
of `std::unordered_map` when pointer stability isn't needed, and
`absl::node_hash_map` when it is. Both will still generally perform
better and require less overhead than `std::unordered_map`.
Notably, the guide says: "Note that this advice never suggests the use
of `std::unordered_map` and `std::unordered_set`. These containers
provides similar features to the Abseil flat hash containers but with
worse performance. They should only be used if absolutely required for
compatibility with third-party code.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Replace `std::unordered_map` with `absl::flat_hash_map`.
The Chromium containers guide
(https://chromium.googlesource.com/chromium/src/+/HEAD/base/containers/README.md)
recommends using `absl::flat_hash_map` as a default map choice instead
of `std::unordered_map` when pointer stability isn't needed, and
`absl::node_hash_map` when it is. Both will still generally perform
better and require less overhead than `std::unordered_map`.
Notably, the guide says: "Note that this advice never suggests the use
of `std::unordered_map` and `std::unordered_set`. These containers
provides similar features to the Abseil flat hash containers but with
worse performance. They should only be used if absolutely required for
compatibility with third-party code.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |