Replies: 2 comments 5 replies
-
Hello @lokiiiii what those plugins do ? For the moment, there is no rate control on the Glances API, so if a client asks for stats several time per second than the Glances server try to answer by consuming more CPU cycle. |
Beta Was this translation helpful? Give feedback.
5 replies
-
Just implement a basic TTL (set to 1 second) for the API cache in the develop branch of Glances: #3202 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello everyone,
My glances and homepage are both up-to-date docker versions and when I declare one glances widget in homepage, the glances' python3 process is ok at around 7% cpu but as soon as I declare two or more widgets, python3 process is around 150% and can even go as high as 600% sometimes...
I already opened a ticket on homepage's side and it seems that this issue may be related with multiple API calls to glances.
Is anyone experiencing the same ?
Thanks
Beta Was this translation helpful? Give feedback.
All reactions