Implementing the fast extension (BEP6) can also be useful to avoid some complications in the accounting of pending requests. Since you already implemented PEX you also must have BEP 10 implemented, make sure to honor the reqq field in that case. Implements more bittorrent specifications? are you getting the IP addresses correctly?ĭo peers immediately disconnect the client - which would indicate a bug or missing piece in your protocol implementation - or other network errors during connection setup?ĭo you get any incoming (remote-initiated) connections? If not you'll have to forward your TCP listening port or implement UPnP-IGD or PCP in that case. Are you processing the peer sources (DHT, tracker) correctly, i.e. Well, that's where I'd would start to compare. When the client try to download something, it can find more than 1000 peer addresses, but just can connect only around 30 peers, and some of them response very slowly. To snapshot the current buffering state of sockets you can use ss -tie. Wireshark is also a useful tool to look at bittorrent and TCP at the network level. libtorrent and some clients based on it provide that, so does biglybt. To start with you'll want to use a client with very fine-grained logging as reference so you can understand their behavior. So you will have to investigate and compare your client with another from many angles. BitComet EZ Booster is just an extremely.enhancing the speed. Besides supported bittorrent features and correct implementation of the specification there also are things such as inefficiently implemented socket programming that could slow you down. BitComet EZ Booster is just an extremely strong add-on with the most up-to-the-minute approach. We don't see your client in action, so we don't know why it is slow.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |