[Plugin] ltConfig v2.1.1

[Ratanak]

Edit of original first post by ambipro (Deluge Team Member, Moderator, and Developer)

ltConfig is a plugin for Deluge that allows direct modification to libtorrent settings.

• Currently tested with all current PyPi published .whl files from win_amd64 on all version of Deluge 2.x
• ratanakvlun handed the project down to mhertz (another mod here) - and he gave it to me (ambipro) - and I am now the current maintainer/owner.

This plugin adds a preference page to both GtkUI and WebUI and the latest version (2.1.0 of ltConfig) is fully compatible with Deluge 2.x. with Python3

Original v2.0.0 ltConfig from ratanakvlun's GitHub (abandoned)
Repository: github.com/ratanakvlun/deluge-ltconfig
Downloads: github.com/ratanakvlun/deluge-ltconfig/releases


Maintained and Current Repository
Current Repository: https://github.com/zakkarry/deluge-ltconfig
Releases: : https://github.com/zakkarry/deluge-ltconfig/releases
Current .egg direct download: https://github.com/zakkarry/deluge-ltco ... tag/v2.1.1

To convert your Deluge 2.x or upgrade libtorrent on Windows, simply download the appropiate .whl from PyPi below and replace it in its location in Deluge's directory in Program Files. Otherwise simply install a version without lt2 in the filename from the Download section of this site.

Simply rename the .whl extension to .zip and extract the .pyd file, then with Deluge exited replace it in its location in your "Program Files" directory.

Latest libtorrent 1.2.19 .whl(Python 3.9)
Latest libtorrent 1.2.19 .whl (Python 3.10)

Linux users, simply use pip to switch versions.

Source: viewtopic.php?p=235167#p235167

Modify settings at your own risk!

If you are on Deluge 1.x, please consider an upgrade to Deluge 2.x - it's far better

Deluge with libtorrent 1.2.x is the version without "lt2" in the filename.

The explanation of the settings and suggested values (with context of PC hardware and bandwidth is available at [TUNING] ltConfig Settings and Explanations stickied post if you want to granularly micromanage them.

Performance, memory usage, and general CPU usage is handled much better on 1.2.x. The current/latest .whl file is 1.2.19 and can be found on can be found from PyPi @ the above links or by going to PyPi.org PyPi.org's platform file repository - simply choose win_amd64 and the version of python you use - if above 3.10 then use cp310, it should work.

The default should be cp39 last time I checked.

For official documentation (the post on these forums above is a better source, the official documentation is rather technical and does not document the outcome of changes made, but if you want to see official docs, information about each setting, see the libtorrent manua/documentationl.

The original libtorrent GitHub by arvidn can be found here: libtorrent's GitHub.

The main difference between 2.x and 1.x is the disk and memory usage, memory mapped files are used in 2.x and the previous OS caching methods have been removed. Large torrents, or a large quantity of torrents, while utilizing libtorrent 2.x are not going to heed the caching settings that normally would be set in Deluge's menu (or ltConfig). This results in Deluge using an outstanding amount of memory (and on Windows showing memory usage without being associated with Deluge.exe itself). See one of the more popular github issues here in regards to the 2.0 caching/memory mapping Issue 6667: "Libtorrent 2.x memory-mapped files and RAM usage"

Thus 1.2.x is recommended, although it appears no more PyPi compiles are being done in the CI even though further patch versions of libtorrent 1.2.x are being published, as they are now 2 minor versions behind without publishing on PyPi and the workflows have not been updated to publish new 1.2.x versions to PyPi.

Older versions of libtorrent and ltConfig's profiles may have different settings. You can get some info on your specific version by visiting the original ratanakvlun repository and grabbing older versions of the .egg.

To make sure changes persist, modify this plugin's preference page to "apply on start". Modifying any of the Deluge preference pages at the same time may trigger a Deluge callback that could override some of the libtorrent settings set by this plugin. Examples would be simultaneous http requests (announce) and caching settings on libtorrent 1.2.x.

New in version ltConfig 2.1.0 - new added profile with the settings from the ltConfig libtorrent profile values explanation and recommendation from ambipro, under zakkarry's preset seen in the screenshot above or in the explanations' post above.


Changelog (Full):

Version 2.1.0

• - Fixed some bugs with selecting checkboxes with cursor/mouse clicks
  - Added updated profile settings for modern bandwidth and hardware (High Performance Seed and zakkarry's settings modified)
  - Fixed some settings not applying immediately for caching options

Version 2.0.0

• - Update to support Deluge 2.x and Python 3

Version 0.3.1

• - Fix hang when using Deluge from Debian 9 repo
  - Improve compatibility of presets
  - Restart network services when settings changed

Version 0.3.0

• - Add support for dict settings (lt >= 0.16.x)
  - Add libtorrent defaults preset
  - Change version to semantic versioning

Version 0.2.5.0

• - Add support for DHT settings

Version 0.2.4.1

• - Fix ltConfig not trying to use Deluge's libtorrent first
  - Fix libtorrent version checking

Version 0.2.4.0

• - Add preset support (from https://github.com/omaralvarez)
  - Allow columns to be resized in GtkUI

Version 0.2.3.0

• - Add WebUI support
  - Fix apply button not applying if apply on start is disabled

[jkaberg]

hey ratanak

nice plugin you got there, think you could implent

Code: Select all

bool lock_files;

with that? check http://www.rasterbar.com/products/libto ... tomization

[Ratanak]

nice plugin you got there, think you could implent

Code: Select all

bool lock_files;

The plugin just enumerates the settings returned by libtorrent (there is no fixed handling of any particular setting). The setting should already be exposed if your version of libtorrent supports it. The "lock_files" setting in particular is supported starting from libtorrent 0.16.0.

If you are using Deluge on Windows, you can try updating your libtorrent by downloading an installer (.msi) from here. Make sure you get the right one for your Python version (Deluge 1.3.5 for Windows comes with Python 2.6). Run the installer and when it is done, copy the "libtorrent.pyd" file from the install location to your Deluge folder. You may want to make a backup of the original that's already in the Deluge folder just in case you want to revert back to the old version. After a restart of Deluge, it should now be using the updated libtorrent version.

[three18ti]

Thanks Ratanak,

Just wanted to say this worked great for me on two different hosts with lib torrent versions 0.15.10.0 and 0.16.3.0 in deluge 1.3.6.

[Darlok]

This is a fantastic plugin Ratanak, thank you kindly for sharing.

[Phixion]

Anyone know why this plugin isn't displaying in the UI for me?

Running Wheezy / Python 2.7

[Ratanak]

Version updated to 0.2.

There are now additional columns that give a better idea of what settings are in effect. There is a column that allows the user to select which settings will be applied, a column that shows the current user setting (or if the setting is disabled, the original value at time of plugin start) and a column with the current actual libtorrent settings.

Also in this update, there is an option to toggle whether the settings are applied on startup so the user can choose not to have the settings automatically applied. By startup, it is meant the start of the plugin and not the daemon.

[jorricks]

I can't set a single setting..
I will show you what I mean with a screenshot
http://imageshack.com/a/img855/3477/4f73.jpg
When I tried to chance the value 500 to something else, I get the bar that normally you got instead of 500 with 500 in it, now in the right bottom somewhere, blank, without anything in it.
I entered "3....." just as example..
I can't apply this value somehow..
I can't get it off the 500..

[Ratanak]

jorricks, you have to check the box in the first column if you intend to modify a setting.

[jorricks]

NVM! I understood it wrong,
First enable the check box, then instead of trying to chance actual chance setting xD
OOPS
Thanks for the help!