-
-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reduce memory overhead in the cht #79
Conversation
- Perform GC-only rehashing to remove tombstones. - Shrink capacity when possible. Relates to #72.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Merging. Will tune the performance parameters later.
Hello! I have come to you after much debugging. I don't know why, but the logic gated by this code causes
If I change the
Results before changing it showed this:
You'll notice the batch size is locked at I'm happy to share the code I'm using for running this benchmark. Would it be possible to make these settings tunable? What do they even mean? Can you think of anything that would solve my problem? I care more about the blocking nature of evictions than I do memory usage (depending on just how much more and the exact trade-off). I am doing I think ~6k inserts per second on an async Moka cache that can hold however many elements cuz I am bounding it by size in bytes of up to 8GB. Thank you for any help |
Relates to #72.