Skip to content
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

[Bug Report] Dashboard high CPU usage #574

Open
niker opened this issue Jan 30, 2023 · 0 comments
Open

[Bug Report] Dashboard high CPU usage #574

niker opened this issue Jan 30, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@niker
Copy link

niker commented Jan 30, 2023

Describe the bug
I have 19 docker containers running on my machine and yesterday I thought I got hacked and someone installed a cryptominer background process.
After some detective work I discovered the 30-80% CPU usage is caused by process
/usr/bin/python3 /usr/bin/uvicorn
which is running under Yacht. And the very dashboard I was using to diagnose the issue was causing the massive load.
This load is present even if the dashboard is not the active page which is confusing.
The dashboard also seems to load in 3 separate stages, as if the command times out and the rest is fetched on second/third try.

To Reproduce

  1. Use a low power machine like a PI4B
  2. Install sufficient number of containers (about 20+)
  3. Fry some eggs :)

Expected behavior
Not sure if this is a bug or inefficiency in the polling process but suffice to say portainer barely uses any CPU time in comparison. Maybe the polling rate could be slowed down by configuration and the dashboard hardly needs refreshing when it's not an active page or yacht is not the active browser tab.

Screenshots
obrazek

Desktop:

  • OS: Ubuntu Server
  • Browser Firefox latest
  • Yacht Version v0.0.7-alpha-2023-01-12--05
@niker niker added the bug Something isn't working label Jan 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant