New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

V4.1.4 CPU capped // speed capped #9965

Open
pleasedontbetakendamn opened this Issue Dec 3, 2018 · 8 comments

Comments

Projects
None yet
5 participants
@pleasedontbetakendamn

pleasedontbetakendamn commented Dec 3, 2018

Please provide the following information

qBittorrent version and Operating System

v4.1.4 on a Windows 10 Home v1803 installation.

What is the problem

qBittorrent 4.1.4 is cpu capped, maxing out 1 core. The result is that I can't use more than 2 Mbit/s of my entire connection, because qBittorrent is maxed out on available cpu resources.

What is the expected behavior

Above 500 Mbit/s download speeds.

Steps to reproduce

Install qBittorent 4.1.4 on a 8C SMT enabled AMD Ryzen / 64 GB ram. This is also a 100% fresh installed OS with all the new updates.

@Seeker2

This comment has been minimized.

Seeker2 commented Dec 4, 2018

CPU limitations was mentioned at:
https://qbforums.shiki.hu/index.php/topic,3956.0.html EXTREME Speed Tests of various BitTorrent Apps
...as a limiting factor for max DL or UL speeds.
But it should be much faster than 2 megabits/second.
Do you mean 2 MegaBYTES/second instead?

@pleasedontbetakendamn

This comment has been minimized.

pleasedontbetakendamn commented Dec 4, 2018

2 Mbit/s or about 200 kBytes/s down with 200 seeds connected on TCP only. My 4.1.4 client is capped at 1 kBytes/s on all connected seeds/peers. Same with upload.
I could download faster from a peer, but only if the client didn't hit the 100% usage on its available resources. After the cap, all connections hit 1 kB/s maximum transfer.

4 Mbit/s with TCP and uTP combined.

edit: Okay so the 4.1.4 client is eating up CPU on the TCP protocol only. The uTP protocol on the other hand used almost zero resources, but this protocol is capped at 1.5 MegaBytes/s download.

@pleasedontbetakendamn pleasedontbetakendamn changed the title from V4.1.4 CPU capped to V4.1.4 CPU capped // speed capped Dec 4, 2018

@sledgehammer999

This comment has been minimized.

Contributor

sledgehammer999 commented Dec 4, 2018

Something's wrong with your setup. Yes, libtorrent is CPU bound but nowhere near 1Mb/s. People have reported downloading using fiber connections.
I would suggest you make sure that you have the latest official driver for the network card you're using. Not the generic microsoft one that Windows might install.
What is the bandwidth you get from your ISP?
Do other software in your machine achieve bigger speeds? Is a CPU core still at 100% etc

@pleasedontbetakendamn

This comment has been minimized.

pleasedontbetakendamn commented Dec 4, 2018

The only thing wrong with my setup is that I installed 4.1.4. Most of the others versions are (edit: working) fine, while 4.1.4 is eating up so much CPU on 1 core, that it can't handle itself and gets speed capped.

@Rootax

This comment has been minimized.

Rootax commented Dec 6, 2018

I do around 100-105mo/sec with 4.1.4 on my 1gb fiber and my little I3-8100, with the cpu not working a lot. Even with my "old" i3-4010 I was around 70-80mo/sec (under windows x64, x64 QBT version, and an SSD as destination directory), but with the cpu nearly dying :o

@pleasedontbetakendamn

This comment has been minimized.

pleasedontbetakendamn commented Dec 6, 2018

Everything is easy against 1 single seed/peer. Try with 500 connections or 2000.

@Rootax

This comment has been minimized.

Rootax commented Dec 6, 2018

Who talked about 1 seed / peer ? I was just saying that FOR ME, I've no problem with speed, just for the record. Even with a lot of connections (but If I may, if you have 500 connections per torrent, I guess it wouldn't be very efficient.. I cap mines around 200, and 2000 totals.)

@sandersaares

This comment has been minimized.

sandersaares commented Dec 8, 2018

It might be insightful to have an understanding of what the particular thread is doing. Do you know how to capture a stack trace with symbols? If so, please post a few of the busy thread (at different points in time).

If you do not know how to do that, here are some step by step instructions.

  1. Download and run Process Explorer.
  2. Open qBittorrent properties in Process Explorer and make a note of the TID of the thread that is the CPU bottleneck.
  3. Create a few minidumps at different points in time when your process looks to be CPU bottlenecked. Post these as attachments here (you may need to zip them).

image

image

From the dump files, we might be able to detect what qBittorrent is doing when it is keeping your CPU busy.

Note that the dump files may expose parts of the qBittorrent memory (configuration, paths, data about torrents in progress etc). Do not post them if you have any sensitive data you may want to keep from strangers on the internet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment