-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
docs: badger in config.md #8662
Conversation
flatfs. | ||
- This datastore uses up to several gigabytes of memory. | ||
`flatfs`. | ||
- This datastore uses up to several gigabytes of memory. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we should give some examples of repo sizes at which the memory consumption degrades to the point of being useless, so people have a better idea if it even makes sense for their use case.
Anecdotal evidence: ipfs/distributed-wikipedia-mirror#85
Do we have more data on this?
@johnnymatthews mind taking a quick look at markdown changes here? (only 15 lines) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Made some minor edits, but I'm fine with them not being committed before merge. They're mainly just formatting and sentence structure.
This should fix the issue of users thinking badger is "no-brainer faster choice" and then running into problems.
Co-authored-by: Johnny <[email protected]>
72cf11a
to
c4b7595
Compare
Thanks! The company behind badger is closing (https://discuss.dgraph.io/t/quitting-dgraph-labs/16702) so I'm merging this so our new users are not baited into trying badger. |
This is copy-paste from ipfs/kubo#8662 to ensure consistency.
This is copy-paste from ipfs/kubo#8662 to ensure consistency.
This is copy-paste from ipfs#8662 to ensure consistency.
This is copy-paste from ipfs#8662 to ensure consistency.
This is copy-paste from ipfs#8662 to ensure consistency.
This is copy-paste from ipfs#8662 to ensure consistency.
This PR updates docs with current status of badger,
which should fix the issue of users thinking badger is "no-brainer faster choice for repos bigger than 10GB"
...and then running into problems.
TODO
/docs/config.md
in this repoipfs config profile --help
and http://docs.ipfs.io.ipns.localhost:8080/reference/cli/#ipfs-config-profile 🙃