I am running extension version 2.0.0 in Deluge 2.1.1 with libtorrent 2.0.5.0.
Startup time is very slow, from the time the daemon accepts connections or the graphical interface responds to user input. From the application debug output, I learn that in this interval the application queries all trackers for each torrent. With many torrents active, this process is quote long, but it is not necessary or optimal these operations to occur synchronously.
Perhaps the issue is upstream. with the application, but I would request a design modification with the external interface to the application available with asynchronous operations for the tracker queries.
I am running extension version 2.0.0 in Deluge 2.1.1 with libtorrent 2.0.5.0.
Startup time is very slow, from the time the daemon accepts connections or the graphical interface responds to user input. From the application debug output, I learn that in this interval the application queries all trackers for each torrent. With many torrents active, this process is quote long, but it is not necessary or optimal these operations to occur synchronously.
Perhaps the issue is upstream. with the application, but I would request a design modification with the external interface to the application available with asynchronous operations for the tracker queries.