• 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 CPU Usage "Capped" at 25%

thealex

New Pleskian
We released tickets for sale on one of our sites today, we dont have Cgroups or any other "limiting plugins" on our plesk instance, we also had speedkit (which is a waste of time, basically was instantly used its 15GB bandwidth then was doing nothing.

We had about 300k page requests from cloudflare over the past 24 hours aswell.

Running on 16 Thread, 32GB Memory instance, but CPU would not go over 25%, plesk control loads quick as, but site was crashing all the time, is there some inbuilt rate limiter on each individual site? or some other thing causing a virtual limit of 25% usage.

Shows the same in Htop aswell.
 
No. What does the actual per thread breakdown look like? Is this a VPS, where the host may be throttling? Do you have a proc limit/PHP worker bottleneck?
 
You might not have the Plesk cgroups plugin, but you can still have cgroup limiting in place in your operating system, because that's a function of your OS, not of Plesk. What's the output of
# systemctl show httpd | grep CPU

I would not recommend to allow httpd to get 100% cpu share anyway, so maybe you could also just run
# systemctl set-property httpd CPUAccounting=true
# systemctl set-property httpd CPUQuota=90%
and see if this solves the issue.

The above assumes that your Apache runs as httpd. On Debian, Ubuntu it is probably named apache2.
 
what is your iowait, and load average? If all your tasks are waiting for I/O, there won't be much CPU time used.
 
It could also be that your Apache's ServerLimit (and other related parameters) are too low. Once the ServerLimit or max. number of threads/childs has been reached, it will no longer accept new connections until others are closed.

That might explain the 'limit' of 25% CPU usage.
 
It could also be that your Apache's ServerLimit (and other related parameters) are too low. Once the ServerLimit or max. number of threads/childs has been reached, it will no longer accept new connections until others are closed.
Doesn't apache log something in that case?
 
Back
Top