[GH-ISSUE #564] Which list should the average user choose? #455

New issue

Closed

opened 2026-02-26 06:30:38 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 06:30:38 +03:00

Owner

Originally created by @OvercookedBeef on GitHub (Jan 19, 2025).
Original GitHub issue: https://github.com/ngosang/trackerslist/issues/564

Now that https://github.com/qbittorrent/qBittorrent/pull/21828 was merged, I am wondering which list I should use. It seems in the past (9 years ago!) you recommended using the UDP list if you don't have any issues with UDP trackers: https://github.com/ngosang/trackerslist/issues/7#issuecomment-225372496

Is this still the case, or should I use best / all / http / https instead?

Also, is there any reason to use best over all? There's obviously more bandwidth with all but other than that?

Originally created by @OvercookedBeef on GitHub (Jan 19, 2025). Original GitHub issue: https://github.com/ngosang/trackerslist/issues/564 Now that https://github.com/qbittorrent/qBittorrent/pull/21828 was merged, I am wondering which list I should use. It seems in the past (9 years ago!) you recommended using the UDP list if you don't have any issues with UDP trackers: https://github.com/ngosang/trackerslist/issues/7#issuecomment-225372496 Is this still the case, or should I use best / all / http / https instead? Also, is there any reason to use best over all? There's obviously more bandwidth with all but other than that?

kerem

2026-02-26 06:30:38 +03:00

closed this issue
added the
question
label

kerem commented

2026-02-26 06:30:39 +03:00

Author

Owner

@rautamiekka commented on GitHub (Jan 19, 2025):

I'd just use the 'all' list.

^ If there's any client that'll have a problem, that client is most likely nothing more than a "I made it cuz I could" project, and thus shouldn't even be used.

@rautamiekka commented on GitHub (Jan 19, 2025): I'd just use the 'all' list. ^ If there's any client that'll have a problem, that client is most likely nothing more than a "I made it cuz I could" project, and thus shouldn't even be used.

kerem commented

2026-02-26 06:30:39 +03:00

Author

Owner

@ngosang commented on GitHub (Feb 15, 2025):

In the last 9 years the hardware has become cheaper and more powerful. I think most trackers today don't have any problems with millions of users. Said that, I will elaborate a bit.

trackers_all:

This list contains all trackers I know. This includes duplicate trackers (some trackers listen on HTTP, HTTPS and UDP ports but return the same peers). It also includes small trackers that don't return peers in many cases.
Pros: You will find many peers. This is really useful for you and for the swarm when sharing old torrents.
Cons: You will make many requests/connections. This will increase the load on your system and in the trackers. But as I said before, with the current hardware is not a big problem.

trackers_best:

This list is recommended for popular/new torrents. It contains only the best 20 trackers (with more peers, and more reliable). It's more than enough to find peers and you won't make as many requests.

trackers_all_udp:

The UDP protocol uses less resources in the client and in the server. But as I said before, with the current hardware this is not a big problem.

Just choose "all" or "best" list. If your goal is to share torrents for a long time, I recommend "all" list.

@ngosang commented on GitHub (Feb 15, 2025): In the last 9 years the hardware has become cheaper and more powerful. I think most trackers today don't have any problems with millions of users. Said that, I will elaborate a bit. **trackers_all**: * This list contains all trackers I know. This includes duplicate trackers (some trackers listen on HTTP, HTTPS and UDP ports but return the same peers). It also includes small trackers that don't return peers in many cases. * Pros: You will find many peers. This is really useful for you and for the swarm when sharing old torrents. * Cons: You will make many requests/connections. This will increase the load on your system and in the trackers. But as I said before, with the current hardware is not a big problem. **trackers_best**: * This list is recommended for popular/new torrents. It contains only the best 20 trackers (with more peers, and more reliable). It's more than enough to find peers and you won't make as many requests. **trackers_all_udp**: * The UDP protocol uses less resources in the client and in the server. But as I said before, with the current hardware this is not a big problem. Just choose "all" or "best" list. If your goal is to share torrents for a long time, I recommend "all" list.