Optimal Settings for Magnets? Extremely slow in v3.2 (Build 27886)

[backpackla]

Torrents loaded from magnet links are extremely slow VS. torrents loaded from *.torrent files.

Here is my current setup:

In "Connection" settings, the only option I have enabled/ticked is "Add Windows firewall exception".

In "BitTorrent" settings, I have the following enabled:

* DHT network

* DHT for new networks

* uTP

* UDP tracker support

The following are DISABLED:

* Local Peer Discovery

* Ask tracker for scrape

* Enable peer exchange

* Limit local peer bandwidth

Protocol encryption is DISABLED for outgoing, ENABLED for incoming legacy connections

Port forwarding is set up correctly (*.torrent stuff running fine).

Anything I can change to improve speeds?

[lovetour]

Magnet links need more time to find sources if the magnet links does not specify trackers.

DHT or local peer discovery are the first ways that uTorrent uses to establish sources. (enable both Local Peer Disovery and DHT for best performance). If DHT is working, it can take varying lengths of time to find sources and other data about the torrent, depending on how many sources there are. I am not an expert on DHT inner workings, so I don't know, but there might be a chance that there are a small number of sources in some cases and your current DHT peers have no pathway to discovering them at a given time. You can wait for the situation to improve. I have personally never seen this happen, but I don't access rare files via magnet very often.

After at least one peer was discovered via DHT and Local Peer Discovery, uTorrent will try to connect to it/some of them. The number of connections attempted at one time may depend on various connection settings.

After establishing a connection with at least one peer, if you have Peer Exchange (PEX) enabled (definitely enable peer exchange for reasonable magnet performance), uTorrent will ask that peer for a list of other peers. That peer may or may not provide a list, or may provide only a partial list, but this feature is commonly enabled and is the only way uTorrent can find more peers beyond what DHT and local peer discovery know about, if you are not using trackers.

uTorrent protocol is irrelevant - it is generally a good thing though. It is a protocol used when supported to help prevent uTorrent network traffic overwhelming you or the other client's network connections -- it helps force bittorrent traffic to be treated with a lower priority and yield to other internet traffic like web browsing to the degree it can.

"Limit Local peer bandwidth" is not usually relevant. Even local peer discovery, depending on network topology (home routers, ISP network design, etc.) can even discovery other peers on the internet, but if they are on the Internet (rather than on your LAN) they will not be treated as local peers for the purpose of this setting. Local peer bandwidth pertains to your LAN.

Tracker settings likely are irrelevant to your case, as if trackers are indeed included in the magnet links you are using, they will be utilized the same for all purposes related to performance as if you had downloaded an actual torrent file.

Edit: If you enable protocol encryption, for the best performance in most cases (as it will allow you to connect to the greatest number of peers), enable/check "Allow incoming legacy connections." and do not set outgoing encryption to "Forced".

[backpackla]

Thank you for that very informative response! I've changed my settings per your recommendations.

Magnet links need more time to find sources if the magnet links does not specify trackers.

DHT or local peer discovery are the first ways that uTorrent uses to establish sources. (enable both Local Peer Disovery and DHT for best performance). If DHT is working, it can take varying lengths of time to find sources and other data about the torrent, depending on how many sources there are. I am not an expert on DHT inner workings, so I don't know, but there might be a chance that there are a small number of sources in some cases and your current DHT peers have no pathway to discovering them at a given time. You can wait for the situation to improve. I have personally never seen this happen, but I don't access rare files via magnet very often.

After at least one peer was discovered via DHT and Local Peer Discovery, uTorrent will try to connect to it/some of them. The number of connections attempted at one time may depend on various connection settings.

After establishing a connection with at least one peer, if you have Peer Exchange (PEX) enabled (definitely enable peer exchange for reasonable magnet performance), uTorrent will ask that peer for a list of other peers. That peer may or may not provide a list, or may provide only a partial list, but this feature is commonly enabled and is the only way uTorrent can find more peers beyond what DHT and local peer discovery know about, if you are not using trackers.

uTorrent protocol is irrelevant - it is generally a good thing though. It is a protocol used when supported to help prevent uTorrent network traffic overwhelming you or the other client's network connections -- it helps force bittorrent traffic to be treated with a lower priority and yield to other internet traffic like web browsing to the degree it can.

"Limit Local peer bandwidth" is not usually relevant. Even local peer discovery, depending on network topology (home routers, ISP network design, etc.) can even discovery other peers on the internet, but if they are on the Internet (rather than on your LAN) they will not be treated as local peers for the purpose of this setting. Local peer bandwidth pertains to your LAN.

Tracker settings likely are irrelevant to your case, as if trackers are indeed included in the magnet links you are using, they will be utilized the same for all purposes related to performance as if you had downloaded an actual torrent file.

Edit: If you enable protocol encryption, for the best performance in most cases (as it will allow you to connect to the greatest number of peers), enable/check "Allow incoming legacy connections." and do not set outgoing encryption to "Forced".