Skip to content
This repository has been archived by the owner on Dec 18, 2024. It is now read-only.

scaling/limits/performance #96

Open
thisconnect opened this issue Oct 21, 2017 · 1 comment
Open

scaling/limits/performance #96

thisconnect opened this issue Oct 21, 2017 · 1 comment

Comments

@thisconnect
Copy link

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?

@aphelionz
Copy link
Collaborator

Moving this to the Field Manual to go into more details

@aphelionz aphelionz transferred this issue from orbitdb/orbitdb Sep 27, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants