Skip to content
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

rocksdb high cpu usage due to LRU cache contention? #13081

Closed
zaidoon1 opened this issue Oct 18, 2024 · 3 comments
Closed

rocksdb high cpu usage due to LRU cache contention? #13081

zaidoon1 opened this issue Oct 18, 2024 · 3 comments

Comments

@zaidoon1
Copy link
Contributor

We can see a strong correlation between increasing the number of block cache HITs and the amount of cpu used by rocksdb:

Screenshot 2024-10-18 at 12 59 33 AM Screenshot 2024-10-18 at 2 02 55 AM Screenshot 2024-10-18 at 1 05 22 AM Screenshot 2024-10-18 at 1 42 35 AM

Is this expected behaviour? And is there a fix for this? Is switching to hyper clock cache the only way to truly fix this?

@mdcallag
Copy link
Contributor

The big win comes from using hyper clock.

Smaller improvements might be possible from using more shards in the LRU block cache assuming that your problem is a hot shard rather than a hot block.

@zaidoon1
Copy link
Contributor Author

zaidoon1 commented Oct 19, 2024

got it, that's good to know! I've started rolling out the change to use hyper clock cache. I'll keep this issue open for now and will post a before/after

@zaidoon1
Copy link
Contributor Author

zaidoon1 commented Oct 30, 2024

Before (LRU cache):

Screenshot 2024-10-30 at 2 10 53 AM

After (Hyper clock cache):

Screenshot 2024-10-30 at 2 12 43 AM

Very happy with the results here. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants