You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Use a low power machine like a PI4B
Install sufficient number of containers (about 20+)
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
Desktop:
OS: Ubuntu Server
Browser Firefox latest
Yacht Version v0.0.7-alpha-2023-01-12--05
The text was updated successfully, but these errors were encountered:
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
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
Desktop:
The text was updated successfully, but these errors were encountered: