I have a script that compares Deluge stats with the tracker stats and here is a very typical example of its output:
Analysis is complicated since tracker stats sometimes have low resolution and are delayed by a few minutes, but the script compensates as well as possible (the columns are explained below the table)
- Items #10 and #12 have losses of 0.5 hours AND sizable upload credit (286 and 452 MB respectively); for those, the analysis is consistent over many samples and the loss is not a transient effect).
- Items #10 and #10 are RSS triggered torrents. No doubt the first 30 minutes of tracking is lost, which is usually the peak upload interval since seeding competition is the least then.
- Having 10 to 20% affected torrents is typical. I've not seen torrents lose more than one interval. Nor have I seen losses except immediately after creation. Only RSS triggered torrents have been affected in my observations.
I'm hesitant to turn on tracing because I've read that it is rather a fire hose, and I'd have to trace for days for analysis. Are there any suggestions how to more "surgically" isolate the fault here (to Deluge or the tracker or seedbox or to whatever)?