Hmm... I have gotten really strange speeds at the tracker. The total speed is 300 Kb/s, it shows 7. Another file has 12 Kb/s, it shows 90. It did the same with 1.7, but it is still like that in 2.0 ... any solutions?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The speed calculation is a sliding window average and with never show exactly what the peers are seeing. Even in the original PHPBTTracker it was never meant to be an 'accurate' statistic for the speed.
With it's default interval setting in config.php it will take into account the speed average over the last 20 minutes. If there is a constant influx of peers on a new torrent the speed will rise gradually over an hour or so and be 'close' to that of the swarm. This of course depends on the peers reporting correctly to the tracker. If you have people leave the torrent rapidly, this can also affect this calculation.
Just keep in mind that this was not meant to be a super-accurate calculation. :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I should mention that at the default interval, if the speed truly stays at 300Kb/s for 30-45 minutes or so, this value would be reflected on the statistic page. It's when it flucuates up and down that causes the sliding window to not be accurate.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The tracker uses the original calculation from the original phpbt. The only difference between it and this one is that instead of disabling the speed calculation altoghether you can change it's interval. If this interval is changed it may affect the accuracy on the speed stats (as it can take longer for the average to 'catch up'.)
I don't understand what you mean by the scrape value "shows the throughput of all files together". The extra stats (if this is what you are referring to) provided in scrape will show the same stats as on the tracker page.
The original phpbt has the same warning regarding the tracker speed. It says in one of the files that the speed will likely be understated most of the time.
I myself do not have your speed problem on my test server, so it is hard for me to figure out what is wrong.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hmm... I have gotten really strange speeds at the tracker. The total speed is 300 Kb/s, it shows 7. Another file has 12 Kb/s, it shows 90. It did the same with 1.7, but it is still like that in 2.0 ... any solutions?
The speed calculation is a sliding window average and with never show exactly what the peers are seeing. Even in the original PHPBTTracker it was never meant to be an 'accurate' statistic for the speed.
With it's default interval setting in config.php it will take into account the speed average over the last 20 minutes. If there is a constant influx of peers on a new torrent the speed will rise gradually over an hour or so and be 'close' to that of the swarm. This of course depends on the peers reporting correctly to the tracker. If you have people leave the torrent rapidly, this can also affect this calculation.
Just keep in mind that this was not meant to be a super-accurate calculation. :)
I should mention that at the default interval, if the speed truly stays at 300Kb/s for 30-45 minutes or so, this value would be reflected on the statistic page. It's when it flucuates up and down that causes the sliding window to not be accurate.
Well...yes, i thought it is like that...But, there is the scrape value, that shows the throughput of all files together.
So, the tracker doesnt use that value, but it calculates the values of the last 20 minutes and displays an average of those... hmm...
Don't want to be rude, but we used the original phpbt and it displayed the speeds correctly. Is there are possible cause?
just btw I asked the question, now registered.
The tracker uses the original calculation from the original phpbt. The only difference between it and this one is that instead of disabling the speed calculation altoghether you can change it's interval. If this interval is changed it may affect the accuracy on the speed stats (as it can take longer for the average to 'catch up'.)
I don't understand what you mean by the scrape value "shows the throughput of all files together". The extra stats (if this is what you are referring to) provided in scrape will show the same stats as on the tracker page.
The original phpbt has the same warning regarding the tracker speed. It says in one of the files that the speed will likely be understated most of the time.
I myself do not have your speed problem on my test server, so it is hard for me to figure out what is wrong.