fails to pin to the working tracker within a tier

[sledgehammer999]

Some users are reporting that tracker announcements with correct upload/download stats aren't happening correctly.
Libtorrent version used is 1.1.5+gitd52763805c

Relevant qbt bug: qbittorrent/qBittorrent#8108
The first post has some pictures showing the discrepancy between client and tracker stats. It is quite big.
Others report that correct stats are reported after torrent completion and during seeding, but the uploaded stats that happened during download aren't reported and are "lost".

[arvidn]

there are simulation tests that assert that announces happen at the right times. I will look into those to make sure they are correct and would cover this case, but I feel pretty confident they do.

It would be really helpful if someone experiencing this problem could post a log exposing this issue
(that means announce logs with the relevant query parameters and torrent state transitions)

[ignitionnight]

@arvidn I emailed you at your libtorrent address with the an attached log, the email subject is "issue #2724 log"

I downloaded a torrent from private tracker broadcasthe.net and seeded for about two and a half hours. qbittorrent reports 39.5 MiB uploaded, but the tracker only reports 11.1 MB. This experience is consistent with the issues that I originally reported in the qbittorrent issue tracker qbittorrent/qBittorrent#8108.

I downloaded a torrent almost immediately after it was loaded to the site. There were already 30ish seeds before I started leeching, but I was seeding in about a minute. After the first update on the tracker it showed only 3 MB of upload despite the qbittorrent reporting ~30 MiB uploaded.

I tested this against utorrent 2.2.1 and under similar circumstances the upload credit was 100% correct, any additional upload I contributed after an update on the tracker was reflected on the site within 30 minutes following the next update.

Thank you, and let me know if you need anything else.

[arvidn]

just to rule things out; are you confident that the number qBittorrent told you was correct?
There are more than one way to report uploads. Perhaps qBittorrent shows you total uploaded bytes, whereas what's reported to the tracker is only payload upload. i.e. all the protocol overhead for downloading does not count from the tracker's point of view.

[greenbench]

Is it possible that the difference between total uploaded bytes and only payload upload can be hundreds of megabytes - almost gigabyte? Because that's the difference i'm getting with popular torrents. Then again, before qB 4.0.x that has never happened before. All upload was 100% matched.

[arvidn]

anything's possible :) I would guess that protocol overhead in the upload direction is about 2-3% of the downloaded payload. Assuming qBT hasn't made any recent changes in what it reports though, it does seem plausible that it's the reporting to tracker where the problem lies.

[greenbench]

Weird. I mean, i see peers are downloading from me in real time, but then it's announcing to tracker and no upload reporting.

[ignitionnight]

I'd agree with Greenbench. Although I don't know enough to disagree with Arvid, it really doesn't feel like that would be the case when some torrents work successfully and update correctly and others don't.

I notice this issue with upload stats mostly with highly seeded very new torrents, which happens to me often because I have RSS autodownload set up. Is the issue per chance that upload between initial download and the first announce after beginning seeding isn't being reported?

[greenbench]

Here is how it goes for me:

1. torrent added. first announce to tracker. torrent started downloading and uploading.
2. torrent finished. second announce to tracker. download amount reported correctly but no upload reported. peers are downloading from me and uploading continues.
3. third announce to tracker. no upload reported. peers are downloading from me and uploading continues.
4. fourth announce to tracker. upload amount that was between third announce and that one reported correctly. and from that it's all correct, beside that was "lost" between first and third announces.

and my "fix" for that was:

1. torrent added. first announce to tracker. torrent started downloading and uploading.
2. torrent finished. second announce to tracker. i paused the torrent. download and upload amount reported correctly. (EDIT: it's no more than 3 seconds, but all upload between the time of the second announce and the time i paused the torrent is not reported)
3. started the torrent. third announce to tracker. upload amount reported correctly from now on.

[greenbench]

second announce to tracker. i paused the torrent. download and upload amount reported correctly.
started the torrent. third announce to tracker

quoting myself here. i honestly can't tell if there is another announce between those two.

[arvidn]

@ignitionnight I had a look at your log. I can't find anything obviously wrong with it (but there is one peculiarity).

It shows starting the download with an announce of &left= of about 436 MB and &downloaded= 0.

Once you complete the download (27 seconds later), there's an &event=completed announce with &uploaded= 3828300 (i.e. about 3.8 MB) and &left=0.

The next regular announce (about 2 hours later) has &uploaded= 41454753 (i.e. about 41MB).

Am I correct in assuming that what qBT is reporting is a lot higher than that?
You mention how the upload during the download is lost. Since you completed the download in 27 seconds, 3.1MB of upload doesn't seem outrageously small, was it more in reality?

41 MB in 2 hours is an average upload rate of ~5.7kB/s, which isn't very much. But also not obviously wrong, in case there's a lot more supply than demand.

The one odd thing I found was the download reporting. The complete announce reported a donwnload counter ~70kB greater than the subsequent announce. It sounds a bit far fetched that this would be related though, but let me know if you can think of something.

[sledgehammer999]

In order to provide a bit of info on what qbt presents to the user:
There are 2 places where such info is displayed.

1. A per torrent "General" tab info at the bottom of the tranferlist.
   There the info is printed as "total size (session size)". For total size we use torrent_status::all_time_download and for session size we use torrent_status::total_payload_download
   (same thing for upload)

2. In the transferlist as separate columns for total/session which use the same values as above.