Deluge
Yes, mhertz's updated high performance are there, mhertz handed over maintaining this plugin to me and I added mine, which are described above and much more in line with the sort of config you would expect to need with hardware similar to mine.
I use deluge on a server with thin client, but this doesn't affect the ltConfig you choose. If you just read the entire post it explains my hardware setup. My config is, in almost all cases, better than the high performance seeder profile which mhertz updated from the libtorrent settings (he did not create it)
[TUNING] ltConfig Settings and Explanations
Re: [TUNING] ltConfig Settings and Explanations
Thanks for the clarification, and sorry for the late reply.
I tried your configuration and it’s been working really well. Compared to the stock presets and the mhertz profiles, I’m seeing better overall performance!
The only change I did is to enable use_write_cache since I’m on an HDD (like you said in the documentation).
Appreciate the effort you put into maintaining and documenting the config. Thanks for sharing it
I tried your configuration and it’s been working really well. Compared to the stock presets and the mhertz profiles, I’m seeing better overall performance!
The only change I did is to enable use_write_cache since I’m on an HDD (like you said in the documentation).
Appreciate the effort you put into maintaining and documenting the config. Thanks for sharing it
Re: [TUNING] ltConfig Settings and Explanations
Just to be clear, mhertz brought the default configs from libtorrent's library. He did not create the profiles previously added (low memory, high perf seed, default) - they are all just updated along the way as libtorrent changed things in their repository.
I'm the first, and only, person as far as i'm aware that has documented the settings en mass and provided values different.
You can check the repository for libtorrent yourself, both 2 and 1 variants have their own high perf seed settings and others. mhertz did a good job of maintaining parity, but I have spent time in the clients developing for Deluge and cross-seed, and gained a good knowledgebase around what each does...and I just wanted to bring that to the Deluge community, but since qBittorrent was mostly the same I decided to provide the advanced page for them as both clients use libtorrent-rasterbar.
I've got a config for libtorrent-raksasha (rtorrent) - but the user-base for it is much smaller and varies greatly, and the users of rTorrent and raksasha are generally power users themselves to the 10th degree. I don't feel comfortable as a new users, even with my knowlege, instructing them like I do rasterbar.
Glad you had success, I've been in talks with linuxserver and binhex about adding it, updated Stats.egg and my geoip.dat ( https://geo.el0.org ) into their images, and it now seems to have them incorperated, bringing much better lifecycle to containerized users. I'd like to see the default latest go to libv1 though rather than 2. libtorrentv2 is a good change (memory mapping files) in theory, but the OS's aren't ready for the technology and methods and v1 of libtorrent is definitely much more performant, which I maintained a version of until I had talked both container maintainers into providing a v1 base container - now to give it dominance!
I'm the first, and only, person as far as i'm aware that has documented the settings en mass and provided values different.
You can check the repository for libtorrent yourself, both 2 and 1 variants have their own high perf seed settings and others. mhertz did a good job of maintaining parity, but I have spent time in the clients developing for Deluge and cross-seed, and gained a good knowledgebase around what each does...and I just wanted to bring that to the Deluge community, but since qBittorrent was mostly the same I decided to provide the advanced page for them as both clients use libtorrent-rasterbar.
I've got a config for libtorrent-raksasha (rtorrent) - but the user-base for it is much smaller and varies greatly, and the users of rTorrent and raksasha are generally power users themselves to the 10th degree. I don't feel comfortable as a new users, even with my knowlege, instructing them like I do rasterbar.
Glad you had success, I've been in talks with linuxserver and binhex about adding it, updated Stats.egg and my geoip.dat ( https://geo.el0.org ) into their images, and it now seems to have them incorperated, bringing much better lifecycle to containerized users. I'd like to see the default latest go to libv1 though rather than 2. libtorrentv2 is a good change (memory mapping files) in theory, but the OS's aren't ready for the technology and methods and v1 of libtorrent is definitely much more performant, which I maintained a version of until I had talked both container maintainers into providing a v1 base container - now to give it dominance!