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.

Sign up for GitHub

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

Jump to bottom

[kvdb-rocksdb] configurable column memory budget #135

Closed
dvdplm opened this issue May 6, 2019 · 0 comments · Fixed by #256
Closed

[kvdb-rocksdb] configurable column memory budget #135

dvdplm opened this issue May 6, 2019 · 0 comments · Fixed by #256
Labels
F6-refactor hacktoberfest Join us for hacktoberfest - https://substrate.dev/hacktoberfest/ P7-nicetohave Q1-mentor Q2-easy

Comments

@dvdplm
Copy link
Contributor

dvdplm commented May 6, 2019 •
edited

Currently in kvdb-rocksdb the memory budget is split evenly across all column families. In reality many use cases store data very unevenly across CFs, e.g. in parity-ethereum probably 90% of the data exists on the state CF.

Make the memory budget distribution configurable or settable on a per-CF basis.
@ordian ordian changed the title [kvdb-rocksdb] configurable memory budget [kvdb-rocksdb] configurable column memory budget May 6, 2019
@gnunicorn gnunicorn added the hacktoberfest Join us for hacktoberfest - https://substrate.dev/hacktoberfest/ label Sep 24, 2019
@ordian ordian mentioned this issue Nov 8, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
F6-refactor hacktoberfest Join us for hacktoberfest - https://substrate.dev/hacktoberfest/ P7-nicetohave Q1-mentor Q2-easy
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

kvdb-rocksdb: configurable memory budget per column paritytech/parity-common
3 participants
@dvdplm @gnunicorn @ordian