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

scaling/limits/performance #96

Open

thisconnect opened this issue Oct 21, 2017 · 1 comment

Labels

thisconnect commented Oct 21, 2017

what are the practical or theoretical limits of orbit-db (or ipfs)?

how many keys can one put in the kv store?

how many values can a key have?

does having either many keys and/or values have impact on

read speed?
write speed?
memory

does a node need the full db to read/write?

Member

aphelionz commented Sep 27, 2019

Moving this to the Field Manual to go into more details

aphelionz transferred this issue from orbitdb/orbitdb

aphelionz added the Thinking P2P label

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