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

Enable jemalloc support in rocksdb #6290

Closed
matklad opened this issue Feb 14, 2022 · 2 comments · Fixed by #7456
Closed

Enable jemalloc support in rocksdb #6290

matklad opened this issue Feb 14, 2022 · 2 comments · Fixed by #7456
Assignees
Labels
Node Node team P-medium Priority: medium T-node Team: issues relevant to the node experience team

Comments

@matklad
Copy link
Contributor

matklad commented Feb 14, 2022

After #6289, we should be able to take advantage of rust-rocksdb/rust-rocksdb#542 – making rocks aware that the allocator we use is jemalloc. Intuitively, it seems like that might bring some substantional perf wins.

@matklad matklad added the T-node Team: issues relevant to the node experience team label Feb 14, 2022
@bowenwang1996
Copy link
Collaborator

Sadly we reverted #6289 as the performance of 0.18 is worse than that of 0.16 according to our benchmark

@nikurt nikurt self-assigned this Jun 14, 2022
@exalate-issue-sync exalate-issue-sync bot added the P-medium Priority: medium label Aug 11, 2022
@akhi3030
Copy link
Collaborator

#6351 upgraded back to 0.18. We have been running on 0.18 for some time now.

near-bulldozer bot pushed a commit that referenced this issue Sep 19, 2022
We’re using jemalloc in Rust code so it makes sense to do the same in
RocksDB.

Fixes: #6290
nikurt pushed a commit that referenced this issue Nov 9, 2022
We’re using jemalloc in Rust code so it makes sense to do the same in
RocksDB.

Fixes: #6290
@gmilescu gmilescu added the Node Node team label Oct 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Node Node team P-medium Priority: medium T-node Team: issues relevant to the node experience team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants