Deluge
Libtorrent 2.0.8 update.
Re: Libtorrent 2.0.8 update.
Thanks Mhertz! I swapped out and the performance gain on download speeds with 1.2.19 is very noticeable and appreciated.
Re: Libtorrent 2.0.8 update.
I know this is old. But i am curious if there's been some development. Is lt 2 working better now or is 1.2.X still preferred?
Re: Libtorrent 2.0.8 update.
I prefer 1.2.19, and based on my testing it performs better. This is not a one-size-fits-all analysis though, so if you really want the best for you, you have to just test it out and see what works.
2.x will _ALWAYS_ use substantially more memory during torrenting due to memory mapping, it just will. Outside of the mechanisms we've discussed on here like cgroups for linux, and the wlimit plugin for windows to artificially limit it's memory usage, it basically has no "limit" on the amount of your free memory libtorrent will use. It will return it if the OS requests allocation, but I still don't want to run at 90-100% memory usage if I don't have to.
It's good in theory (2.x) but it just doesn't work out in practice, particularly if you do anything else on the PC running it. qBittorrent artificially limits it in its own way, its a known "flaw", mostly caused by poor implementations of memory mapping in at the OS layer. It just is what it is, it was ambitious for arvidn to use it in 2.x, but maybe down the road it will work out better. I dont know.
In the mean time, if you want to use any of the caching settings in ltConfig or Cache (preferences) - then you will have to use 1.2.x, Deluge was built around it and 2.x just was made available because it was a drop in replacement more or less.
I will be recommending only 1.2.x for the foreseeable future, until something changes in all these regards.
2.x will _ALWAYS_ use substantially more memory during torrenting due to memory mapping, it just will. Outside of the mechanisms we've discussed on here like cgroups for linux, and the wlimit plugin for windows to artificially limit it's memory usage, it basically has no "limit" on the amount of your free memory libtorrent will use. It will return it if the OS requests allocation, but I still don't want to run at 90-100% memory usage if I don't have to.
It's good in theory (2.x) but it just doesn't work out in practice, particularly if you do anything else on the PC running it. qBittorrent artificially limits it in its own way, its a known "flaw", mostly caused by poor implementations of memory mapping in at the OS layer. It just is what it is, it was ambitious for arvidn to use it in 2.x, but maybe down the road it will work out better. I dont know.
In the mean time, if you want to use any of the caching settings in ltConfig or Cache (preferences) - then you will have to use 1.2.x, Deluge was built around it and 2.x just was made available because it was a drop in replacement more or less.
I will be recommending only 1.2.x for the foreseeable future, until something changes in all these regards.