Does Ktorrent do any kind of special buffering of disk writes? I'm a bit concerned with several concurrently downloading torrents (having several threads each) constantly writing to different places on the disk causing its heads to move frequently, and thus causing extra wear.

We use memory mapped IO, which gives the kernel a lot of freedom in what to write when.

Hello!

My disk light is always on with Ktorrent.. Not a good news.

Memory Map is not so good for Ktorrent when download/upload with very high speed. Few reason:

1. If you use filesystem ntfs-3g, they do not support delay-write, which means that write operation is never cached. Using ntfs is very normal when download multimedia. But maybe I'm wrong here.

2. The buffer kernel provided by default is very very very conservative. The default read_ahead_kb is 128k. When downloading with 10M/s, I don't you think that's enough? People will not try to optimize their kernel options so much...

Is something changed in this matter? If not will it be better to change to utorrent for lesser disk wear?

To my knowledge there have not been any changes. Based on the log at https://projects.kde.org/projects/extra ... /revisions it would appear that KTorrent is no longer being actively maintained.

bcooksley wrote:To my knowledge there have not been any changes. Based on the log at https://projects.kde.org/projects/extra ... /revisions it would appear that KTorrent is no longer being actively maintained.

It also appears that KTorrent.org has no longer been functional for some time now as well. Perhaps it's time to look at other options to be the default in KDE, such as the actively developed qBittorrent?