Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-62786

Investigate replacing MurmurHash3 with CityHash where possible

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Do
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Storage Execution

    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.

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            dan.larkin-york@mongodb.com Dan Larkin-York
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: