[SERVER-62786] Investigate replacing MurmurHash3 with CityHash where possible Created: 20/Jan/22 Updated: 06/Dec/22 Resolved: 07/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dan Larkin-York | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
There are a few performance-sensitive places in our codebase where we still use the outdated MurmurHash3 algorithm, where we could replace it with the more efficient CityHash algorithm (i.e.from absl::hash). Some uses of MurmurHash3 must be preserved, as the hash value is stored persistently or shared across the network and must be consistent between nodes. But for some uses, the value is local and transient, and can be replaced with any valid hash function. We should determine which uses are safe to replace, and evaluate the performance impact of these replacements. |