High CPU usage and bad performance on Raspberry PI
Posted: Fri Aug 30, 2013 7:26 am
I decided to use a raspberry pi as a torrent box. Seemed doable, plus there are many sites on the internet saying they've done it.
I've got the latest raspberian on my PI. I copied my deluge config from the machine I was using it on before, installed deluge and started it all up.
I'm only running deluged and deluge-web on the PI.
It runs... but it is extremely slow and unresponsive. When I connect from a different machine using the GTK client, it takes forever to respond and update. As in, if I click on a certain State, it takes AT LEAST to 30 seconds to actually update the list. If I add a torrent it updates it's progress on the same scale, and I think it might be hanging and then restarting the download (I can't tell for sure, it's so painful).
It's also eating massive amounts of CPU - anywhere from 35% to 85%. Even when it's using the lesser amount, it's far from responsive. Hell, I tried to kill the process and THAT took 5 minutes!
Deluge-web is another story. It connects and accepts my password, but claims that the server on localhost is offline. I tried localhost, the server's hostname, the server's IP address... one time it showed online for a minute, but by the time I tried to connect it was offline again. I'm assuming this is related to the performance issue.
Oh, I nuked the packaged version and built 1.3.6 from scratch... same deal.
Anyone?...
I've got the latest raspberian on my PI. I copied my deluge config from the machine I was using it on before, installed deluge and started it all up.
I'm only running deluged and deluge-web on the PI.
It runs... but it is extremely slow and unresponsive. When I connect from a different machine using the GTK client, it takes forever to respond and update. As in, if I click on a certain State, it takes AT LEAST to 30 seconds to actually update the list. If I add a torrent it updates it's progress on the same scale, and I think it might be hanging and then restarting the download (I can't tell for sure, it's so painful).
It's also eating massive amounts of CPU - anywhere from 35% to 85%. Even when it's using the lesser amount, it's far from responsive. Hell, I tried to kill the process and THAT took 5 minutes!
Deluge-web is another story. It connects and accepts my password, but claims that the server on localhost is offline. I tried localhost, the server's hostname, the server's IP address... one time it showed online for a minute, but by the time I tried to connect it was offline again. I'm assuming this is related to the performance issue.
Oh, I nuked the packaged version and built 1.3.6 from scratch... same deal.
Anyone?...
