Custom Query (2449 matches)

I've noticed that Deluge 0.5.8.4 keeps flushing the data back to the drive almost immidiately after it receives it. It also seems to read data for uploading as it's needed. With just one torrent going 100KB/s down and 50KB/s up my HDD LED keeps flashing like crazy. This is very taxing for hard drives. Please make an option available to have the data flushed less frequently (like a slider with some reasonable values and a reasonable default value, say 2MB).

This would reduce writes.

Also, some sort of intelligent and more RAM-heavy (hey, RAM is cheap and it could be optional) uploading mechanism would be in order. Like buffering more data at once, I'm not sure how the protocol works, but parts that have most demand could be pre-emptively cached or/and if there's some sort of a queue, parse who needs what in advance and cache this data in bigger chunks in preperation before sending it.

This would reduce reads.

i am trying the best way to describe it but basically so that for example you could have 1 torrent downloading and two torrents seeding and when the torrent downloading finishes it starts the next one in the queue and the finished torrents goes to seed and it doesn't affect the overall amount of maximum active torrents

another example

Max No. of torrents Downloading: 1 Max No. of torrents Seeding: 3

something setup like that instead of just

Maximum simultaeneus active torrents: 4

Since most projects do it this way and to not interfere with software managed by the system under /usr, I would suggest to change the default install PREFIX to /usr/local.