Skip to content

avoid murmur mixplit when keys are already hashes #47

@RaduBerinde

Description

@RaduBerinde

In many cases the keys are already the result of a good hashing function like murmur or xxhash. It would make sense to avoid the murmur64 mixsplit on each key during building (and on each lookup).

I was thinking we could make it so that filter.Seed=0 means skipping the mixsplit step altogether. We could try that for the first iteration during building; if it doesn't work, we retry with a non-zero seed (and no sorting+removing of duplicates - we can do that if we fail again).

We could make this an option when using the builder.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions