mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
4.4.2 high CPU usage in Docker (raspberry Pi4) #13382
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#13382
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kanedauy on GitHub (May 1, 2022).
qBittorrent & operating system versions
qBittorrent: 4.4.2
Operating system: Linux
Qt: 6.2.4
Libtorrent: 2.0.6.0
Boost: 1.77.0
OpenSSL: 1.1.1n
zlib: 1.2.12
What is the problem?
CPU usage stays at 98%
Steps to reproduce
Additional context
I'm using my older configuration from 4.3.9
Log(s) & preferences file(s)
qBittorrent.conf
@jfabaf commented on GitHub (May 11, 2022):
I have the same problem:
qBittorrent: 4.4.2
CPU: Intel(R) Celeron(R) CPU N3160 (4 cores)
RAM: 4GB
Operating system: Ubuntu Linux 18.04
Docker image: linuxserver/qbittorrent:latest
With 127 torrents but no active torrents CPU usage stays at 30% all the time.
@trankillity commented on GitHub (May 15, 2022):
Also seeing this on my Synology NAS (Celeron J3550/8gb RAM) after setting it up in Docker. Load averages for the NAS are over 2.0 with qBT running, sits at 0.4 without qBT running.
I've only go 12 torrents in there, with a cap of 8 active (3 down, 5 up). Have tweaked my connection count down to 200 to get fewer spikes, but it's still pretty bad.
Got a feeling it could be something to do with disk caching as it also uses a lot of memory and
[kswapd0]process is also frequently high when qBT is running. Imagine it can be solved with some advancedlibtorrentsettings, but not sure where to look for best settings.@James-Kent-l commented on GitHub (May 18, 2022):
You can try version 4.3.9. Trust me, it will improve a lot
@kevindd992002 commented on GitHub (Jan 28, 2023):
Have you ever fixed this? I'm using hotio's legacy (4.3.9) container and I'm having the same issue.
@kanedauy commented on GitHub (Jan 28, 2023):
@kevindd992002 I fixed this using a version that uses libtorrent 1.x, in my case I use the image from linuxserver qBittorrent with libtorrentv1 in the tag
@kevindd992002 commented on GitHub (Jan 28, 2023):
I see. Did ypu have the exact same symptoms as I did? Is there a disadvantage if I don't use 4.3.9 though?
@kanedauy commented on GitHub (Jan 28, 2023):
@kevindd992002 Talking only in from my experience, no disadvantages using >= 4.4 versions, the main feature is support for v2 torrents.
My rule of thumb is if the new version works equal or better, upgrade, if there are disadvantages in your daily use, skip the version.
The platform I use is Raspberry Pi 4, I do not have experience with Synology NAS.
If you keep having issues I recommend to open an issue specifically for your case.
@kevindd992002 commented on GitHub (Jan 28, 2023):
Gotcha. I just realized that the 4.3.9 container I'm using still has libtorrent 1.2. So I'm using the good version of libtorrent. Do you mind sending me over your config (including advanced settings)?
Oh and what are "v2 torrents"?
@kanedauy commented on GitHub (Jan 28, 2023):
bittorrent-v2
This is all my config, I have removed all my info for ###REMOVED###
qBittorrent.conf
@glassez commented on GitHub (Jan 28, 2023):
FYI, libtorrent-1.2 based builds don't support v2 torrents.
@kevindd992002 commented on GitHub (Jan 29, 2023):
Yes. That's what @kanedauy was implying in his post. But is that really a loss?
@glassez commented on GitHub (Jan 29, 2023):
I think still not. It is unlikely that there are currently quite a lot of pure v2 torrents in the wild.