Deluge writing 50 GB per day

[galneon]

I've recently migrated my server's system disk to an SSD. This wasn't an issue in the past, but the 50 GB per day of writes to Deluge's AppData directory is excessive (over 18 TB per year) and will have a tangible impact on SSD life. There would be no problem if Deluge was at least somewhat portable and I could move the /state directory onto an HDD, but that isn't currently possible. I use an enormous cache (deluged always uses about 2 GB), but that's irrelevant as it doesn't affect how frequently torrents.fastresume is written.

I have 1400+ torrents active and have been very happy with Deluge since migrating to it as it's a dream for handling such a high volume of torrents, but the inflexibility of where state data goes is highly problematic, and I'm not the only user who wishes it was more portable.

Is there something I can do to at least decrease the frequency of writes? I'm not one to cry about SSD writes and I use mine to the fullest, but 18 TB per year is absurdly wasteful when performance isn't an issue.

[Shryp]

http://forum.deluge-torrent.org/viewtop ... =7&t=43397

[galneon]

Wow. I had looked last year and turned up nothing. Thank you!

[Cas]

You can also increase the cache: http://forum.deluge-torrent.org/viewtop ... 10&t=37745

[galneon]

Cache was already quite large at 100,000/3,600. I was under the impression that would only affect frequency of writes of download data and not how frequently fastresume is written to the state directory.

Very pleased with the command-line switch now

[Cas]

You are right, I realised later that fastresume writes was the issue you were seeing, good that switch has sorted it