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

Investigate BadgerDB database size #359

Open
AhmadMuzakkir opened this issue Nov 21, 2019 · 1 comment
Open

Investigate BadgerDB database size #359

AhmadMuzakkir opened this issue Nov 21, 2019 · 1 comment
Labels
question Further information is requested

Comments

@AhmadMuzakkir
Copy link
Contributor

AhmadMuzakkir commented Nov 21, 2019 •
edited
Loading

Seems like when using BadgerDB, database size keeps increasing.

I ran the benchmark with 3 nodes, until block 4000. And the size of the 3 databases are 1.3GB.
Not sure if that's normal.

Use PR #353 to enable BadgerDB GC.
@AhmadMuzakkir AhmadMuzakkir added the question Further information is requested label Nov 21, 2019
@rkeene
Copy link
Contributor

rkeene commented Nov 28, 2019

We also stopped using BadgerDB by default in PR #375 we should switch back to BadgerDB after figuring out what's up with the memory usage, which may be related to this issue (if not, we'll split the switching back to a separate issue)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rkeene @AhmadMuzakkir