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

Fix High Memory Usage of RocksDB #1030

Closed
alexanderkiel opened this issue Jun 12, 2023 · 0 comments
Closed

Fix High Memory Usage of RocksDB #1030

alexanderkiel opened this issue Jun 12, 2023 · 0 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@alexanderkiel
Copy link
Member

We observe that the resident memory usage (RSS) of Blaze in certain cases is much higher as the sum of known constituents, the Java memory and the RocksDB block cache memory. Closer inspection revealed that the overhead depends on the size of the RocksDB block cache. The overhead is about 2 - 3 times the size of the block cache.

The root cause is that the default memory allocator of glibc shows high amounts of fragmentation of used in a multi core setting. Switching from glibc to jemalloc (#1014) solved the problem.

@alexanderkiel alexanderkiel self-assigned this Jun 12, 2023
@alexanderkiel alexanderkiel added the bug Something isn't working label Jun 12, 2023
@alexanderkiel alexanderkiel added this to the v0.21.0 milestone Jun 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant