Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-3905

Murmurhash3 implementation is slow on String keys

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Done
    • Icon: Minor Minor
    • 9.0.0.Final
    • 6.0.0.Final, 6.0.1.Final
    • Core

      String instances are a common choice for being used as key entries, still the getBytes() operation being performed allocates costly buffers, and the computation to get those bytes looks like expensive too.

      I suspect there might be good reasons for not using the String's own hashcode directly as an input to Murmurhash? Still that's what other implementations seem to do.

              dberinde@redhat.com Dan Berindei (Inactive)
              sgrinove Sanne Grinovero (Inactive)
              Archiver:
              rhn-support-adongare Amol Dongare

                Created:
                Updated:
                Resolved:
                Archived: