New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Downloading like the wind; uploading next to nothing #10257

Open
n9nu opened this Issue Feb 4, 2019 · 2 comments

Comments

Projects
None yet
3 participants
@n9nu
Copy link

n9nu commented Feb 4, 2019

qBittorrent version: 4.1.5 64 bit
Windows: 10 1809 64 Bit
Issue: Downloading is fast and I achieve the bandwidth I am (in theory) supposed to, however, despite having my UPLOAD rate set to 800KB/sec I never seem to be transmitting or uploading any data. I am 'in the green' with respect to port forwarding and UPnP. This is always the case...whether or not I use ExpressVPN or not. I have a Comcast Business account and even before Comcast with another Wireless ISP I have had little to NO data uploading while downloading like a mofo.

When a file is being SEEDED, I then notice a small amount of upload activity...~100Kbit/sec., however, NOT while I am downloading only. Is this normal OR should I be uploading data with each download? I only download 1 torrent at a time.

Global Upload Bandwidth: 800KB/sec
Incoming connection port: 30000
UPnP & NAT-PMP port forwarding: ENABLED
Global Connections: 710
Connections Per Torrent: 25-30
Global Upload Slots: 35-40
Max Upload slots per torrent: 35-40

DHT: ON
PeX: ON
Asyc I/O Threads: 8
Embedded track port: 6969
Outgoing Ports Min: 0
Outgoing Ports Max: 0

IP Address to report: BLANK. I am using both IPv4 & IPv6
Network Interface: Any Interference - I have the Ethernet port and the loopback
Optional IP address to bind to: All addresses

Tnx

Tim
ARS N9NU

@kennethtran93

This comment has been minimized.

Copy link

kennethtran93 commented Feb 7, 2019

That's generally the state for torrents. Don't forget that you (will be) one of MANY clients transferring a tiny portion/fragment of that data to another peer. It may just be that you don't have a fragment that they need at this time. I would also say that I think the entire downloaded file may be hash-checked first before clients would start seeding it out but I could be wrong here.

Also this issue is not really qbittorrent-relevant but the entire torrent protocol/design itself, so perhaps some further research on your part should be done. Just my two cents here.

@Seeker2

This comment has been minimized.

Copy link

Seeker2 commented Feb 9, 2019

Private torrents hosted by big private trackers have an even worse problem -- a new peer will do a single tracker update, get a small random list of ~1-50 seed ips (out of potentially 100's on the same torrent), and download the whole torrent before doing another tracker update.

Unless your seed is one of the 50 seed ips the new peer got from the tracker, you likely won't upload to it...because when your seed does a tracker update it also gets a random 1-50 peer OR seed ips from the tracker. The more seeds there are, the less likely the new peer's ip is included.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment