Tim Rühsen

Hm, here on Linux, it still shows 10% CPU usage, which is quite high. Can you try with `--progress=none` and report back?

> Using --progress=none drops CPU utilization to 7-12%, with some rare spikes up to 18%. That sounds reasonable downloads via HTTPS and also depends on the utilized network bandwidth and...

Make sense, thanks for the short reproducer.

The progress bar indeed need some love. I just pushed a commit that updates the progress report `[Files: ....` every second. Especially with HTTP/2, a single bar may display completely...

Can you give more details about your clang version and architecture? Because this issue is not reproducible here :) ``` $ clang-18 --version Debian clang version 18.1.8 (12) Target: x86_64-pc-linux-gnu...

Thanks for sharing your thoughts and code. It is up to the user to decide for a hashing function. You can just use the 64bit hash functions and pass any...

> > Thanks for sharing your thoughts and code. > > It is up to the user to decide for a hashing function. You can just use the 64bit hash...

> I don’t see reason why not to use 64bit mask instead of 32. Otherwise we essentially increasing collisions. Correct me if I’m wrong Yes, you are wrong, see my...

> I'm confused by [#77 (comment)](https://github.com/elastic/go-freelru/issues/77#issuecomment-2615803227) > > .. we either have 64bits of entropy or 32bits of entropy.. what else is there to discuss..? we will get fewer collisions...

@pkieltyka One reason two switch to 64bit hash functions would be to simplify the LRU adoption. Currently we have, for example ``` var stringHashFn = func(s string) uint32 { return...