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

Better Broadcasting Strategies #46

Open
tomerk opened this issue Apr 14, 2015 · 1 comment
Open

Better Broadcasting Strategies #46

tomerk opened this issue Apr 14, 2015 · 1 comment
Assignees
@tomerk
Labels
feature

Comments

@tomerk
Copy link
Contributor

tomerk commented Apr 14, 2015

The current broadcasting strategy is to just write into etcd and then read it back from all nodes. Etcd isn't designed for this and this is probably bad for anything over a megabyte in size or so.

Strategies to introduce:

  • Spark filesystem (kinda like how the observations and user weights reading & writing currently work)
  • Torrent

This issue also involves decoupling the Model code from the exact type of broadcast being provided.
@tomerk tomerk added the feature label Apr 14, 2015
@tomerk tomerk mentioned this issue Apr 17, 2015
Merged
@tomerk
Copy link
Contributor Author

tomerk commented Apr 21, 2015

As of Issue #51 Broadcast via the spark filesystem exists.
In the future it would be nice to have broadcast via HTTP, and broadcast via Torrent

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

@tomerk tomerk

Labels
feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tomerk