Transmission

Here's a bit more clever preload library that disables proven defective POSIX_FADV_DONTNEED, but passes POSIX_FADV_SEQUENTIAL and POSIX_FADV_WILLNEED. Just for fun, to see if those other two have any positive impact in the whole picture. I suspect not, but lets see... #define _GNU_SOURCE #include <d...

When loading new data that is to be verified then the kernel will look at all the pages in memory that belongs to cached data and throw out the one that is least used, which could be data that was an earlier part of the torrent is being verified instead of the cached data from another torrent that ...

I hope this response helps you to understand the question I'm asking. It does, and thank you for taking the time to express your concerns clearly. And my apologies if I was a little bit harsh at times, I didn't understand your point completely until now. When I talk about Transmission prefetching b...

[*]Also consider the case where you have a dozen torrents actively seeding when you hit 'verify' on the 4.3 GB torrent. If we flood the cache with the contents of the 4.3 GB torrent, what's that going to do to the cache hit/miss stats on the other torrents?[/list] So, that's our other scenario, whe...

x190's answers are all correct, but allow me to give a shot, too. [*]Consider the use case of a 4.3 GB torrent. The user hits 'verify'. Are the 4.3 GB all going to stay in the cache? No. Are the pieces that stay in the cache the ones that the next peer will need? Yes, they're going to stay in the ca...

I think verify.c does that because it's supposed to be not needed later. One could lobby to have that changed and I've thought about it, but I guess a few hard numbers might help. If you don't request verification, then does it seed from memory? I believe I got devs to fix that part of the equation...

I was glad to see a long list of improvements in 2.80, unfortunately all memory management bugs are still not fixed. :( I tested only the torrent verification. If I do it right after the torrent has completed, it seems to come out of memory cache, so it's fast and efficient. But, then transmission d...

Sure thing, mate. Transmission is a great app, isn't it.

Yeah, those posix_advise(..., POSIX_FADV_DONTNEED) calls are all terribly wrong. Just remove them and all will be fine.

Installed the v2.77 the other day. I'm afraid I see no improvement at all. :( I've attached a 'vmstat 1' session. Notice how there's ~223MB of memory at the beginning. It's like that all the time, the memory is fully utilized. A few seconds into the session I picked an active 2GB torrent and clicked...

Good news x190! In what version will the fix land, so I can test it properly?

Any tool that can show memory usage in real time will do. I like 'vmstat 1' in terminal. Typically memory is completely used (very low numbers in the free column in the vmstat output), not surprising because when there are active torrents with decent speed, Linux page cache will cache everything it ...

Let me first say that transmission is definitely the best torrent client out there, and nothing I write below will change that fact. Now, having said that, I noticed that the client does some incredibly stupid things. Namely, when a torrent download (or verification) is finally completed, and thus t...