johnnyg wrote:Is that the value reported by Deluge or is that value calculated by the tracker?

These specific values are from the tracker.

I see your point but that's less than 1% error, even the transmission one is within 1% error.
I would be interested to see at least one more example possibly with more results from the seed list, and to see what the developers say next...

I noticed that too for a while now... it must have to do with a cache or something.

I'm thinking the best way to describe read/write cache hit ratio is like a grade, a way of telling you how 'good' it is doing based on the files it has cached... with a maximum of 1, being perfect.

Make sure you installed gtk also... it is required.

Did you try 1.2.1 the latest version as of this writing?

Check to see that you are using libtorrent 0.14.9 or greater.

Sounds like a major split or fork to me... if it's even possible.

Don't quote me but, I thought this was already posted in the forum... I think it relies on libtorrent for the feature, and I think that specific feature may be coming in a build soon... as soon as libtorrent gets it deluge shouldn't be too far behind in implementing it.

The problem with this specific example is that deluge has no idea if the data is reliable, or it is what it should be.

Should be fixed in 1.2.1