• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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 Scoreboard full and/or max request workers limit

kevinjansen

Basic Pleskian
Server operating system version
Almalinux 8
Plesk version and microupdate number
18.0.60
Hi All,

I am wondering if there is a max limit a domain can use so we can prevent that a single domain can bring down a server.

We are now seeing sometimes:

server reached MaxRequestWorkers setting, consider raising the MaxRequestWorkers setting
or
scoreboard is full, not at MaxRequestWorkers

The config is:

<IfModule mpm_event_module>
LoadModule cgid_module modules/mod_cgid.so
MaxRequestWorkers 2000
ServerLimit 100
</IfModule>

This is a 12 Core and 48GB server. And when you check the /server-status page its always 1 domain that fills up the entire scoreboard.
I like to find a way (if possible) to prevent that a single domain can bring down a server. We have already capped the max memory limit and cpu cores, but the problem is now moving towards the scoreboard.

So is there a option to say for example a domain is only able to use 200 out of that 2000 workers (10%).
Or how do others prevent that a single domain can bring down a server.

Kind regards,

Kevin
 
Back
Top