• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Meaning of different units in health monitor

Bitpalast

Plesk addicted!
Plesk Guru
In the Health Monitor extension detail charts we are seeing different units on the ordinate for Apache load, Nginx load, mail load, MySQL load and Plesk load. The units (symbols) are:

k
m
no symbol [none]

Should not k be x1000 and m x1000000? However, we we doubt that the system has measured a 5000.0 index on CPU load when it displays "5.0 k", or 200 million load index on mail load when the chart displays "200 m", 2 million load index on Plesk load for "2.0 m" and so on ... All of our hosts have a low load only, so why are the charts showing such high numbers?

What is the true meaning of these ordinate abbreviations?
 
*lightbulb* The "m" is not "Mega", but "milli", so 500 m = 0.5, 450 m = 0.45 and so on.

k still pending. Indeed it looks as this means "kilo" as expected. But than the question is why for rare and short moments the load is measured excessively and unrealistically high while the server is operating trouble-free?
 
Back
Top