High cpu usage during download
Re: High cpu usage during download
I've downloaded some torrent and...here we are...cpu up to 70%. I've to delete again stat folder? Is there some permanent fix?
Re: High cpu usage during download
This must be a bug somewhere. Without being able to reproduce the issue it's nearly impossible to fix. Is it a specific torrent that causes this?
When reporting issues, please include any relevant information such as OS (and version), python version (for Windows users this depends on which Deluge installer was used), Deluge version and plugin version.
Re: High cpu usage during download
No, high cpu usage also exists without any torrents, as I wrote it before. It's certainly a bug, but unfortunately nobody has any idea or solution for that yet. Useless client for me in that state.bro wrote:This must be a bug somewhere. Without being able to reproduce the issue it's nearly impossible to fix. Is it a specific torrent that causes this?
Re: High cpu usage during download
Exactly, it happens with any torrents.
Is there some more infos that i could give?
Is there some more infos that i could give?
Re: High cpu usage during download
Sorry but I do not think your issue is relevant to this topic.Smyl3 wrote:No, high cpu usage also exists without any torrents, as I wrote it before. It's certainly a bug, but unfortunately nobody has any idea or solution for that yet. Useless client for me in that state.
Re: High cpu usage during download
I can create a new separated topic for high cpu usage without any torrents if there aren't any relationship between those problems/bugs, if that helps. Should I?Cas wrote:Sorry but I do not think your issue is relevant to this topic.
Re: High cpu usage during download
If it's the daemon that uses all the CPU you can try to profile it and I can look at the results.
To profile the daemon do this:
To get the absolute path of deluged
Will output something like "/usr/local/bin/deluged"
Then run deluged like this:
If you need to specify a config directory, use -c "path to config dir", e.g.
You can open the profile results with runsnake but I'll gladly look at it.
To profile the daemon do this:
To get the absolute path of deluged
Code: Select all
$ which deluged
Then run deluged like this:
Code: Select all
python -m cProfile -o profile.out /usr/local/bin/deluged -l deluged.log -L info -d
Code: Select all
python -m cProfile -o profile.out /usr/local/bin/deluged -l deluged.log -L info -d -c /home/youruser/.config/deluge
When reporting issues, please include any relevant information such as OS (and version), python version (for Windows users this depends on which Deluge installer was used), Deluge version and plugin version.
Re: High cpu usage during download
Can verify if it's the daemon or client that uses all the CPU?Smyl3 wrote:I can create a new separated topic for high cpu usage without any torrents if there aren't any relationship between those problems/bugs, if that helps. Should I?Cas wrote:Sorry but I do not think your issue is relevant to this topic.
When reporting issues, please include any relevant information such as OS (and version), python version (for Windows users this depends on which Deluge installer was used), Deluge version and plugin version.
Re: High cpu usage during download
Can I? I'm using the windows version of Deluge..bro wrote:Can verify if it's the daemon or client that uses all the CPU?
Re: High cpu usage during download
bro wrote:If it's the daemon that uses all the CPU you can try to profile it and I can look at the results.
To profile the daemon do this:
To get the absolute path of delugedWill output something like "/usr/local/bin/deluged"Code: Select all
$ which deluged
Then run deluged like this:If you need to specify a config directory, use -c "path to config dir", e.g.Code: Select all
python -m cProfile -o profile.out /usr/local/bin/deluged -l deluged.log -L info -d
You can open the profile results with runsnake but I'll gladly look at it.Code: Select all
python -m cProfile -o profile.out /usr/local/bin/deluged -l deluged.log -L info -d -c /home/youruser/.config/deluge
ok, i'll do that. It's necessary to use thin client with deluged daemon?