I love it, but there's a lot of inefficiency there. I can't remember if I mentioned it previously in this thread, but having more feeds active also increases the likelihood of a disconnect, and I currently just use a single feed to keep up with a scenebot.ĭeluge is very busy. Futhermore, I had more disconnects a couple months ago when I had ~5000 seeding torrents than today with ~3000.
I even noticed a significant reduction in disconnects after overclocking said Ryzen from its default clock of 3.1 GHz. I had far more disconnects (it would have been dozens per day if I had bothered to manually reconnect so often) when deluge was running on my old 1st gen Intel Quad 3 GHz than today when I have it on a cheap Ryzen 3.7 GHz. I've been dealing with this for years at this point, and I've noticed it's all related to daemon performance, thinclient seeming to have nothing to do with it beyond being the victim of the disconnects. I like the plugin but I'm unable to use it as of now As long as the feeds are enabled, deluge disconnects from the remote daemon(on the local network) after a short period of time. Seems to have something to do with server loading.Īt the time of disconnect, I saw /var/log/syslog has something similar to what's described here: Some yarss2 settings make it happen more frequently. However, it's especially obvious on slow and heavily IO loaded machine, while less an issue on machines with low loading or high speed IO. I have tried different seedboxes and indeed this plugin causes ThinClient to disconnect. I registered on this forum to second this. Is no one else experiencing these disconnects from the daemon only when YaRSS2 is active? :/
0 kommentar(er)
