Facebook
Twitter-
We value your experience with Plesk during 2024
Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
Please take this short survey:
https://pt-research.typeform.com/to/AmZvSXkx -
The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
-
We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.
Update from 12.0.18 Update #2 to 12.0.18 Update #3 Server health issues
- Thread starter Alex--
- Start date
- Status
I have checked and found that bug PPP-932 is not fixed yet. Fix is planned for next Plesk version.
The problem in that we do not convert jiffies into percent. CPU plugin report data as JIFFIES, not percent.
From collectd FAQ http://collectd.org/faq.shtml()
---------------------------------------------------------------------
Why don't the CPU states sum up to 100%?
Because the CPU plugin does not collect the CPU usage in percent, but rather in "jiffies". A jiffy is the time-unit which the scheduler in the operating systems uses to manage run times of applications. Under Linux, the default configuration is to have 100 jiffies per second, which leads many users to believe they're getting a percentage. You can, however, configure your kernel at compile time to use 250 or 1000 jiffies per second, usually resulting in a more responsive system but IO-throughput is decreased. Especially on busy systems, virtual systems and systems with a "tickless kernel" there may not always be the exact number of intended jiffies in one second, resulting in the variance you've notice in the graphs.
By the way, that you see this issue in collectd but not in other similar tools is due to the fact that collectd collects data much more frequently. Over the timespan of five minutes these variations usually even out pretty good and you're being sold a percentage but actually get - jiffies…
---------------------------------------------------------------------
The problem in that we do not convert jiffies into percent. CPU plugin report data as JIFFIES, not percent.
From collectd FAQ http://collectd.org/faq.shtml()
---------------------------------------------------------------------
Why don't the CPU states sum up to 100%?
Because the CPU plugin does not collect the CPU usage in percent, but rather in "jiffies". A jiffy is the time-unit which the scheduler in the operating systems uses to manage run times of applications. Under Linux, the default configuration is to have 100 jiffies per second, which leads many users to believe they're getting a percentage. You can, however, configure your kernel at compile time to use 250 or 1000 jiffies per second, usually resulting in a more responsive system but IO-throughput is decreased. Especially on busy systems, virtual systems and systems with a "tickless kernel" there may not always be the exact number of intended jiffies in one second, resulting in the variance you've notice in the graphs.
By the way, that you see this issue in collectd but not in other similar tools is due to the fact that collectd collects data much more frequently. Over the timespan of five minutes these variations usually even out pretty good and you're being sold a percentage but actually get - jiffies…
---------------------------------------------------------------------
- Status
