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

direct pipe to improve performance #4

Closed
daviddias opened this issue May 28, 2018 · 2 comments
Closed

direct pipe to improve performance #4

daviddias opened this issue May 28, 2018 · 2 comments

Comments

@daviddias
Copy link
Member

Given that the bottleneck today is Bitswap, wouldn't an alternative, but temporary, solution be just opening a libp2p protocol (.dialProtocol(/peer-crdt/1.0.0) that sends the updates all together just like y.js does?

//cc @pgte @fritzy

@pgte
Copy link
Contributor

pgte commented May 28, 2018

Y.js works by doing a handshake, where each side knows what's each others' latest, so that they can send only updates to each other.
Even so, I think we should create this as an alternative to the native DAG sync.
This would require a vector clock per operation (easily achievable).

@pgte
Copy link
Contributor

pgte commented May 29, 2018

Proposal for fixing this and add some scalability features: #5.
Comments are welcome.

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

No branches or pull requests

2 participants