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

update to Badger DB 3.0 #1750

Open
chappjc opened this issue May 13, 2020 · 2 comments · May be fixed by #1948
Open

update to Badger DB 3.0 #1750

chappjc opened this issue May 13, 2020 · 2 comments · May be fixed by #1948

Comments

@chappjc
Copy link
Member

chappjc commented May 13, 2020

https://github.com/dgraph-io/badger#project-status-march-24-2020

v1 -> v2 is breaking

Try it out, adjust our code, and evaluate performance.

Also solve rebuild of pool DB without complete sync of entire dcrdata DB.

@ukane-philemon
Copy link
Collaborator

@chappjc Badger v3 has been released with lots of performance fix and changes.
v2 - v3 is breaking.
v1 - v3 is better?

@chappjc
Copy link
Member Author

chappjc commented Feb 8, 2022

AFAICT, v2 is not actively developed anymore.
The first v3 release was over a year ago now, so it is probably stable. However we have to be careful not to require cgo, which I think takes special build options with v3. Please do look into it. https://github.com/dgraph-io/badger/blob/master/docs/content/faq/index.md#why-do-i-need-gcc-to-build-badger-does-badger-need-cgo
EDIT: oh actually they removed the zstd cgo thing: https://github.com/dgraph-io/badger/releases/tag/v3.2103.1 That's good.

@chappjc chappjc closed this as completed Dec 26, 2022
@chappjc chappjc reopened this Dec 26, 2022
@chappjc chappjc changed the title experiment with Badger DB 2.0 update to Badger DB 3.0 Dec 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants