Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[BUG] Slow reaction times on machine with large core-count

See original GitHub issue

Describe the bug

I recently got access to a dual-socket AMD Epyc 7742 machine with a total of 256 logical cores. One of the first things I did was to install bpytop to monitor system behavior. However, I noticed that bpytop reacts very slowly on this machine. It takes ~10 second for the clock on the top center to update even though I configured an update interval of 1s. Since I never had such a problem on my own machine, my first assumption was that this is somehow related to the high core-count.

To Reproduce

Start bpytop
The loading screen takes about 10 seconds
After the startup sequence, an update also takes about ten seconds.

Expected behavior

I would expect bpytop to update after the configured interval (1s).

Screenshots

I can record a video of the slow update process if my description was not precise enough.

Info (please complete the following information):

bpytop version: 1.0.63
psutil version: 5.8.0
(Linux) Linux distribution and version: Ubuntu 20.04.1 LTS
Terminal used: xfce4-terminal 0.8.10
Font used: Monospace Regular
Python version: Python 3.8.5

Additional context

contents of ~/.config/bpytop/error.log:

12/04/21 (17:09:58) | INFO: New instance of bpytop version 1.0.63 started with pid 1847342
12/04/21 (17:09:58) | INFO: Loglevel set to DEBUG
12/04/21 (17:09:58) | DEBUG: Using psutil version 5.8.0
12/04/21 (17:09:58) | DEBUG: CMD: /home/lennart-ldap/.local/bin/bpytop --debug
12/04/21 (17:10:11) | DEBUG: Collect and draw completed in 10.820735 seconds
12/04/21 (17:10:12) | DEBUG: Init completed in 13.047520 seconds
12/04/21 (17:10:54) | INFO: Exiting. Runtime 0:00:56

Issue Analytics

State:
Created 2 years ago
Comments:6 (4 by maintainers)

Top GitHub Comments

1reaction

aristocratoscommented, Apr 12, 2021

@lbhm I can add an option to disable the CPU frequency check in the next update, since that particular function seems to be consistently slow on all systems I’ve tested, not 5 seconds slow, but usually a lot slower than any other function. Should be a workaround for your problem then too.

Reopening this, otherwise I’m likely to forget 😃

0reactions

aristocratoscommented, Apr 25, 2021

@lbhm @jeanlst Added an option to toggle CPU frequency and a fix for some weird behaviour in the latest psutil in bpytop v1.0.64

Top Results From Across the Web

Slower SQL Server performance after allocating more CPU ...

That way you'll be covered if you're hitting a weird bug or something. ... a sudden performance drop if the VM's RAM allocation...

FAQ on Performance Issues - MuleSoft Help Center

A performance issue is when an application is running slower than you required it to. This could impact response or processing times, like...

Optimizing Performance for Qlik Sense Enterprise - 1858594

Let's say apps load very very slow for the first time. This is where network speed really comes into play. Another example: the...

Performance Best Practices for VMware vSphere 7.0

This book, Performance Best Practices for VMware vSphere 7.0, provides performance tips that cover the most performance-critical areas of VMware vSphere® ...

Troubleshoot self-hosted integration runtime - Azure

A new activity can throw an OOM error if the IR machine experiences momentary high memory usage. The issue might be caused by...