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.

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

[Protocol Design] Scaling Content Routing #21

Closed
ghost opened this issue Jun 26, 2018 · 2 comments
Closed

[Protocol Design] Scaling Content Routing #21

ghost opened this issue Jun 26, 2018 · 2 comments
Assignees
@whyrusleeping
Labels
ready-to-schedule transfered-to-sched

Comments

@ghost
Copy link

ghost commented Jun 26, 2018 •
edited by ghost
Loading

[Protocol Design] Scaling Content Routing

Your Name: @whyrusleeping

Session Type (choose one): design session

Title (a few words): Scaling Content Routing

Abstract (1 sentence up to a couple paragraphs, for Sched): Currently ipfs uses a DHT for all content routing. This works quite well for many use cases and is generally reliable, fast, and durable. The problem we are now facing is that it does not scale well. Sending out provider records for every single block of every file to the DHT uses an obscene amount of bandwidth, not to mention the increased CPU and memory load. To continue improving ipfs, we need to find a better solution.
@ghost ghost assigned whyrusleeping and unassigned whyrusleeping Jun 26, 2018
@ghost
Copy link
Author

ghost commented Jun 27, 2018

Related issue ipfs/notes#162

@daviddias
Copy link
Member

Merged with #7

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

@whyrusleeping whyrusleeping

Labels
ready-to-schedule transfered-to-sched
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@daviddias @whyrusleeping