This question might be moot given the maintenance mode of this project, but I've seen a noticeable increase in sluggishness of stig over the last year on the same hardware. I always keep my OS up-to-date and I use Arch Linux and Sway.
It takes close to two seconds for stig to open or close the details for an existing torrent where transmission-daemon is running locally. Only 5-10 torrents have been added to transmission and none of them especially busy in terms of current traffic. Is this typical for stig these days? Thank you for creating stig and I hope one day you'll release its successor.
Below is my version info. I use the stig-git AUR package, but I tested the PyPI package too and both have the issue on my hardware. I wish I could recall the release that introduced the sluggishness, but time and OS updates when by and I just put up with the issue until today.
This question might be moot given the maintenance mode of this project, but I've seen a noticeable increase in sluggishness of stig over the last year on the same hardware. I always keep my OS up-to-date and I use Arch Linux and Sway.
It takes close to two seconds for stig to open or close the details for an existing torrent where transmission-daemon is running locally. Only 5-10 torrents have been added to transmission and none of them especially busy in terms of current traffic. Is this typical for stig these days? Thank you for creating stig and I hope one day you'll release its successor.
Below is my version info. I use the stig-git AUR package, but I tested the PyPI package too and both have the issue on my hardware. I wish I could recall the release that introduced the sluggishness, but time and OS updates when by and I just put up with the issue until today.
Here are the specs on my dated, but adequate, hardware: