3 ms·
Few more challenges: - seeding a million active torrents (this is entirely possible and needed but drives a lot of architecture) - a UI for a million active t
by dgroshev 2y ago
Few more challenges:
- seeding a million active torrents (this is entirely possible and needed but drives a lot of architecture)
- a UI for a million active torrents
- be nice to trackers (keep-alive, batched reports; again, architecture gets tricky, iirc libtorrent can't do that still)
- correct pipelining
- congestion control on uTP
- I/O scheduling/batching
- testing all of the above
It is quite a lot.
- blacklion 2y agoLooks like we have same experience with torrents :-)
- dgroshev 2y agoYeah. I was working on [0] for a while (I might get back to it when I have more time) and implemented a chunk of the protocol with an eye for a more scalable libtorrent replacement, and it's not entirely trivial. Even things like the piece picker get trickier at scale. [0]: https://dgroshev.com/blog/torrentdyne-encryption/ https://dgroshev.com/blog/torrentdyne-encryption/