http://home.arcor.de/burzer/download.png

Is this a bug or 'working as intended'? If it's not a bug, could someone explain to me why?

Or am I simply mistaken that a higher average up speed means a ratio greater than 1.0?

I could be wrong, but is the time nothing happens in the calculation? When not...this could be the explanation.

Take a 10 minutes download. You download the whole time at average of 16,1kb. This makes 9660 kb. Now you upload 313 seconds at average of 26,3kb and the other time nothing happens. This makes ca. 8231kb of uploaded stuff. Now calculate 8231/9660....this makes a ratio of 0,85

Burzer wrote:http://home.arcor.de/burzer/download.png

Is this a bug or 'working as intended'? If it's not a bug, could someone explain to me why?

Or am I simply mistaken that a higher average up speed means a ratio greater than 1.0?

Share ratio is calculated on the number of bytes uploaded and downloaded. Not on the average speeds, but you would expect to have a share ratio > 1.0 . Because average upload speed is calculated over the entire time that the torrent was running, average download speed is calculated over the time when you are downloading.

This is strange, can you post the other stats of that torrent ?

George wrote:Because average upload speed is calculated over the entire time that the torrent was running, average download speed is calculated over the time when you are downloading.

To be completely honest, I think that's pretty confusing behaviour. Perhaps sensible, but definately confusing.

More stats (it's the first torrent in the list):
http://home.arcor.de/burzer/ktorrent.png

KTorrent version is 2.0.2 on KDE 3.5.4

Burzer wrote:

George wrote:Because average upload speed is calculated over the entire time that the torrent was running, average download speed is calculated over the time when you are downloading.

To be completely honest, I think that's pretty confusing behaviour. Perhaps sensible, but definately confusing.

If you do not stop calculating average download speed after seeding has begun, it will continuously drop because it will allways be 0 when you are seeding.

More stats (it's the first torrent in the list):
http://home.arcor.de/burzer/ktorrent.png

KTorrent version is 2.0.2 on KDE 3.5.4

You are still downloading this torrent, so the time used to calculate average up and download speed is the same.

So there is definately something wrong with average speeds. Did anything unusual happen, like a crash ?

George wrote:If you do not stop calculating average download speed after seeding has begun, it will continuously drop because it will allways be 0 when you are seeding.

Then I misunderstood you, sorry. In fact, I forgot what I thought you meant. Oh well.

George wrote:So there is definately something wrong with average speeds. Did anything unusual happen, like a crash ?

No, not that I remember. I set my KDE to start with a previously saved session, and KTorrent is part of that. So usually it starts and exits when I boot / shut down my computer. Occasionally I quit KTorrent when I need the upload speed, but most of the time it just runs in the background. Nothing out of the ordinary.

Also, I updated to a SVN version of KTorrent (dont ask me wich one exactly, I just used this KTorrent Gentoo SVN Ebuild) and the bug (?) is still there.

For each torrent, KT creates a temporary directory named torX where X is a number. In each torX dir is a file named stats, the time the torrent has run is saved in that file.

The torX's directories are normally located in ~/.kde/share/apps/ktorrent unless you changed the temporary directory in the settings dialog.

Can you post the stats file of this torrent ?

http://home.arcor.de/burzer/stats.txt

You have imported some parts of this torrent. That explains it. When you calculate average speed, you cannot take the imported bytes into account, because the average speed of the imported bytes is infinity.

Ok. thank you.