-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
SURVEY: Who is using Badger? #1352
Comments
Hey, I'm a developer on dcrandroid, it's a Decred Android Wallet and it has a gomobile backend in dcrlibwallet. I use Badger as permanent storage for wallet and blockchain data which is kind of a lot for mobile but Badger kind of makes it possible. I have my Badger implementation as a driver, my database interface require a bucket so there's a bucket implementation.
I've reduced my config to this but I keep getting that error and I have no idea what to do about it.
|
Hey @C-ollins, since you've set |
It works now but writing get stuck as soon as I get this log, then it freezes till the app shuts down without a reason. I've changed the version to the latest release(not sure if this will conflict with my previous db?) and I've also tried setting sync writes to false but it keeps freezing after I get this log.
Full config
|
@C-ollins I don't see anything crashing. Can you please create a new issue with all the details? I would be happy to help. |
|
We're using it mostly as a SQLite replacement where we don't actually need SQL and temporary-ish storage like logs, HTTPS certificates storage and mail storage.
Yes! compression and encryption were the main reasons we upgraded to V2. We also like its rsync-ability, which was one of the pros for switching from Boltdb.
Typically up to a few GiBs compressed before rotation or deletion.
The only one open-sourced so far is https://github.com/oyato/certmagic-badgerstorage |
Hey @jarifibrahim, I hope the IPFS team is alright that I write a bit about the usage of badger in go-ipfs. I wrote a little about the use-case of go-ipfs here.
go-ipfs uses badger v1 as a replacement for writing files flat out on the disk. It is used as temporary storage as well as permanent storage.
Using badger greatly improves the performance of ipfs compared to using the default filestore.
ipfs does not use those features.
The amount of data varies, from user to user. I think most home users will add just several GB, while servers probably store multiple terabytes in badger in the foreseeable future - since support for it is marked stable just for a short while.
|
Github issues have been deprecated. |
无法使用,当我清理数据之后,给同样的key 重新添加数据, 以前的部分旧数据又会回来,这样的项目start 9.3k 确定不是开玩笑的? |
I am using Badger as the storage layer for Rony framework. Rony is a scalable RPC framework which copies distributed database architecture but in application layer. In other words, it let us write apis in a sharded/replicated manner, hence we can write distributed apps with no need of a separate scalable database. github.com/ronaksoft/rony |
go-ssb is using Badger, which renders it useless on iOS devices, because it attempts to mmap 2GB of data, which will never work on an embedded device. |
Hey there 👋, we're doing an informal survey to gauge the interest in this project and it would be very helpful if you could answer the following questions-
Thank you for your help in improving Badger!
The text was updated successfully, but these errors were encountered: