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

Optimize RocksDB layout for multiple tables #94

Closed

cswinter opened this issue Dec 19, 2018 · 0 comments · Fixed by #164

Labels

Owner

cswinter commented Dec 19, 2018

The tablename should be part of the RocksDB primary key so scans over a column that exists in multiple tables doesn't read unnecessary blocks.

cswinter added the performance label

cswinter mentioned this issue

Custom database backend #164

Merged

cswinter closed this as completed in #164

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment