[low prio]3.3.0alpha CPU usage #2786

Closed
opened 2026-02-21 16:24:37 -05:00 by deekerman · 9 comments
Owner

Originally created by @Ofunniku on GitHub (Jul 14, 2015).

Reposted as a new issue from my last post in #2968:

As soon as I got home I backed up my qbt settings and downloads, and proceeded to I install and run the program. It works and does not freeze, though I'm not too pleased.

I went on to download a large package (70GB) let it run for a few hours, I haven't encountered any stalls or crashes, though I am not too happy with its CPU usage.

Resource Monitor

Usage is higher the higher the transfer speed is. While not high, it is significantly higher than the previous build you provided in this thread. (http://builds.shiki.hu/temp/qbittorrent_v3.2.0_libtorrent0.16.7z)

By comparison, the 3.2.0 libtorrent 0.16 build showed an "average" of 1.xx in Resource Monitor and the CPU frequency was almost always at the lowest state.

I tried installing the older the version and restoring my backup qbt profile and downloads, but all my downloads and settings from my backups don't work, so I'm stuck on this version.

EDIT: This is with the program in the tray, though it hardly makes a difference.

EDIT3: Snipped and moved the issue here.

Originally created by @Ofunniku on GitHub (Jul 14, 2015). Reposted as a new issue from my last post in #2968: As soon as I got home I backed up my qbt settings and downloads, and proceeded to I install and run the program. It works and does not freeze, though I'm not too pleased. I went on to download a large package (70GB) let it run for a few hours, I haven't encountered any stalls or crashes, though I am not too happy with its CPU usage. ![Resource Monitor](http://i.imgur.com/9yBEcHs.png) Usage is higher the higher the transfer speed is. While not high, it is significantly higher than the previous build you provided in this thread. (http://builds.shiki.hu/temp/qbittorrent_v3.2.0_libtorrent0.16.7z) By comparison, the 3.2.0 libtorrent 0.16 build showed an "average" of 1.xx in Resource Monitor and the CPU frequency was almost always at the lowest state. I tried installing the older the version and restoring my backup qbt profile and downloads, but all my downloads and settings from my backups don't work, so I'm stuck on this version. EDIT: This is with the program in the tray, though it hardly makes a difference. EDIT3: Snipped and moved the issue here.
deekerman 2026-02-21 16:24:37 -05:00
Author
Owner

@sledgehammer999 commented on GitHub (Jul 14, 2015):

What is you down speed?

@sledgehammer999 commented on GitHub (Jul 14, 2015): What is you down speed?
Author
Owner

@Ofunniku commented on GitHub (Jul 14, 2015):

At the time that was taken, it was just 500 KB/s more or less.

@Ofunniku commented on GitHub (Jul 14, 2015): At the time that was taken, it was just 500 KB/s more or less.
Author
Owner

@sledgehammer999 commented on GitHub (Jul 14, 2015):

Can you try sorting by the "#" column?
Even it that column is the sorting column, click it again.
Does it make any difference?

@sledgehammer999 commented on GitHub (Jul 14, 2015): Can you try sorting by the "#" column? Even it that column is the sorting column, click it again. Does it make any difference?
Author
Owner

@ngosang commented on GitHub (Jul 14, 2015):

Note: He is using Windows and I'm on Linux.
I'm using the master branch with libtorrent 1.0.5 and the CPU / RAM consumption is ultralow. Downloading at 11.5 MiB/s (100Mbps) only 3% CPU usage and less than 90 MB of RAM.

@ngosang commented on GitHub (Jul 14, 2015): Note: He is using Windows and I'm on Linux. I'm using the master branch with libtorrent 1.0.5 and the CPU / RAM consumption is ultralow. Downloading at 11.5 MiB/s (100Mbps) only 3% CPU usage and less than 90 MB of RAM.
Author
Owner

@Ofunniku commented on GitHub (Jul 14, 2015):

@sledgehammer999 I always sort by that column, and it didn't make a difference either way

@ngosang what's your usage with 3.3.0alpha?

Also, if there is a way to mark this as low priority? I've created a clean new profile and just rolled back to the 3.2.0 libtorrent 0.16 build for now.

I will try the next stable again, and I suppose CPU issues can be ironed out later for 3.3.0?

@Ofunniku commented on GitHub (Jul 14, 2015): @sledgehammer999 I always sort by that column, and it didn't make a difference either way @ngosang what's your usage with 3.3.0alpha? Also, if there is a way to mark this as low priority? I've created a clean new profile and just rolled back to the 3.2.0 libtorrent 0.16 build for now. I will try the next stable again, and I suppose CPU issues can be ironed out later for 3.3.0?
Author
Owner

@ngosang commented on GitHub (Jul 19, 2015):

what's your usage with 3.3.0alpha?

I already answered above. master branch = 3.3.0alpha

@ngosang commented on GitHub (Jul 19, 2015): > what's your usage with 3.3.0alpha? I already answered above. `master branch = 3.3.0alpha`
Author
Owner

@sledgehammer999 commented on GitHub (Nov 9, 2015):

@Ofunniku can you try with latest v3.3.0beta? Link: http://www.fosshub.com/qBittorrent.html

@sledgehammer999 commented on GitHub (Nov 9, 2015): @Ofunniku can you try with latest v3.3.0beta? Link: http://www.fosshub.com/qBittorrent.html
Author
Owner

@Ofunniku commented on GitHub (Dec 2, 2015):

@sledgehammer999 sorry about that, been busy so was unable to report in about this right away and completely forgot.
In the RC, CPU usage is now at around 5% at 500KB/s down with QBT in the tray, so a marked improvement.
Still, lets keep the issue closed, I'll report in again when the release version lands to see if this persists.

@Ofunniku commented on GitHub (Dec 2, 2015): @sledgehammer999 sorry about that, been busy so was unable to report in about this right away and completely forgot. In the RC, CPU usage is now at around 5% at 500KB/s down with QBT in the tray, so a marked improvement. Still, lets keep the issue closed, I'll report in again when the release version lands to see if this persists.
Author
Owner

@ngosang commented on GitHub (Dec 2, 2015):

@Ofunniku v3.3.0 final was released this weekend.

@ngosang commented on GitHub (Dec 2, 2015): @Ofunniku v3.3.0 final was released this weekend.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/qBittorrent#2786
No description provided.