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

about replicate #484

Closed
mccoysc opened this issue Oct 24, 2018 · 4 comments
Closed

about replicate #484

mccoysc opened this issue Oct 24, 2018 · 4 comments
Labels

Comments

@mccoysc
Copy link

mccoysc commented Oct 24, 2018

as i know,every i add some data to db,the orbitdb would publish a json data to the network which in the following format:
{
....,
next:[
.....
]
}

is really that if i have 100000 records in my database,the 'next' field would be in length 100000?
it's so huge……

@haadcode
Copy link
Member

If I understand your question correctly, the next field would contain only 1 hash (next). The length of the log (all entries in the log) would be 100k.

@mccoysc
Copy link
Author

mccoysc commented Oct 25, 2018

but in fact,i found that all hashs of records are in the 'next' field……If i have 100k records or more, maybe the db can wrok well?so huge data transfering via network would be ok?

@mccoysc
Copy link
Author

mccoysc commented Oct 25, 2018

@haadcode

@haydenyoung
Copy link
Member

Large next refs should be addressed in the latest version of OrbitDB. Closing for now but please re-open if problems persist.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants