Resource control

[feross]

Issue by astro
Monday Apr 14, 2014 at 17:44 GMT
Originally opened as https://github.com/feross/bittorrent-client/issues/1

---

I guess a bittorrent-client is basically an aggregation of bittorrent-swarms, right?

So far, I've found no common state requirements, except for resource control:

• Unchoke pooling
• Interested peers limiting (requesting at many peers will consume a lot of memory for incomplete piece messages)
• Peer connection limitation (I have 80+ peers with popular torrents, running multiple of them will make cheap routers break a sweat)
• I/O queuing?
• Bandwidth throttling
• New connection throttling (TCP handshakes require some bandwidth as well)
• UDP throttling

[feross]

Comment by feross
Monday Apr 21, 2014 at 00:31 GMT

---

Yep, all these are good ideas that this module should definitely support. The other thing that is really important is that it needs to have a streaming interface for accessing file contents before the file is fully downloaded. I'm going to push an initial implementation soon.

[feross]

Comment by astro
Monday Apr 21, 2014 at 00:50 GMT

---

Here's how I do it: https://github.com/astro/bitorama/blob/master/lib/file_stream.js

[feross]

Comment by feross
Monday Apr 21, 2014 at 00:54 GMT

---

Thanks, will take a look!