NPROC limit on every account?: Page 3 - Enhance Control Panel

NPROC limit on every account?

gmakhs

wenani thank you, iops are unlimited

gmakhs

cPFence 2 vcpu , unlimited iops , 2 gb ram and it does effect the server greattly if nproc is 100

cPFence

gmakhs
You’re not making use of cgroups with such generous limits. No wonder you’re running into issues.

gmakhs

cPFence do you mind to elaborate please ? Which limit is exesive ?

cPFence

gmakhs do you mind to elaborate please ? Which limit is exesive ?

All of them. You’ll never get things under control with those limits unless you have an extremely powerful server. Use the limits I mentioned earlier as a starting point, monitor performance, and adjust as needed. If a client genuinely needs 2 vCPU and 2 GB RAM, they’re probably not suited for shared hosting anymore. Move them to a small VM instead of compromising the limits for everyone else on the shared server.

gmakhs

cPFence current server has more resources to allocate than that , and it's fairly empty , the issue Is caused from one website, load jumps from 0.60-080 to 70-120, I see that more people are struggling with similar issues, and the fact that same setting on enhance , with cl and same website, shows that something is wrong with the limits, I will keep poking around and hopefully eventually will figure it out .

cPFence

gmakhs current server has more resources to allocate than that , and it's fairly empty , the issue Is caused from one website, load jumps from 0.60-080 to 70-120, I see that more people are struggling with similar issues, and the fact that same setting on enhance , with cl and same website, shows that something is wrong with the limits, I will keep poking around and hopefully eventually will figure it out .

Even if your server has plenty of resources and is mostly empty, a single user can still overload it.

Want to see it in action? Try this:

su - testuser -c "stress --cpu "2" --timeout 3600 &"

Run this command 10-15 times, and you’ll see the impact. ( run pkill -f "stress --cpu" to stop them )

Yes, CloudLinux is far more advanced than cgroups and is an excellent product, but with Enhance’s cgroups combined with containerization, you can get the job done for free if you know what you’re doing and follow best practices. The only real issue you might face is MySQL abuse.

PradeepC

We fixed this with offering unlimited disk I/O and unlimited IOPS with a limited NPROC set to around 30-50 according the plan, and never have faced such issues from past 1 year or so. RAM and CPU are limited though, but even with heavy e-commerce websites generating over $2000 a month, play happily with our 4 vCPU and 4GB RAM shared environment. It depends on how well the site is optimized and the database queries.
As said by @cPFence above, Cloudlinux limits are very different as compared to hard limits cgroups by Enhance.

mike

@gmakhs using the same limits nproc 30 on OLS we had 503. using nginx the website runs smoothly (both without caching). i dunno maybe its how OLS spawns its processes.... (honestly did not try to fiddle/tweak the config in OLS as the changes are lost).

pratik_asabe

Here are our findings after doing months of trials n tests when we switched from cloudlinux to enhance,

First of all, always always prefer dedicated server or VPS with dedicated resources, do not prefer vps with shared cpu unless you're just hosting 1 or max 3 websites with average traffic, also prefer good provider, follow this respectively as per your need and situation.. and always choose NVMe (recomended) or SSD disk..

Use ram:swap in 2:1 ratio, like if your server has 16 GB RAM then use at least 8 GB of swap (again NVMe disk recommended)

then set following base optimization config at bottom in /etc/sysctl.conf
(now, be careful here, you should monitor and if this works for you then great otherwise tweak it till you find stable spot)

vm.swappiness=10
vm.vfs_cache_pressure=100
vm.dirty_background_ratio = 5
vm.dirty_ratio = 20

and lastly,
We typically use this as basic plan to start,

1 vCPU
2 GB RAM
IO Unlimited
IOPS Unlimited
35 or 40 NPROC

Hope this helps... play around you'll find what works best for you...

Vendoz

With 35 NPROC i was in the same boat of the error 503 (using OLS). Than i had to set to 50 for small website and 100 for ecommerce/bigger website, but mall website sometimes gave 503 anyway. So so I turned everything up to 100 NPROC (like i had in Plesk) and now i have no 503, and so I just tune cpu/ram. I'm fine with this config, because a small delay on a website is a lot better than a 503.

pratik_asabe

Vendoz We have a large e commerce site, doing over $4500k/month transactions, and nproc we placed is 50 because before 25 was causing troubles for them, so i can say what kinda server you use plays vital part in it all, resource limit is secondary...

gmakhs

pratik_asabe and you have no server load peaks ?

Vendoz

pratik_asabe It could be, i'm not saying you're wrong, but precisely because you have a large website doing over 4k/month I don't understand the point of taking on the risk of setting 20/30/40/50 NPROCS when you would sleep safely with 100 (and if you're already limiting cpu/ram it will never overload). Black friday sales, christmas, intensive backend operations, analytics, everything could create problems if you're joking with the limit.

In Enhance i only host 60+ sites and I have to migrate another 300+ though the end of 2025, so for me it makes more sense to create a solid setup with as few risks as possible more than to try to limit resources to the minimum possible, otherwise I would be bombarded with tickets or calls. Also because I come from Plesk where 100 NPROC is the default and in fact I had no issue with 503 at all, so even though 100 will be an overkill for many, this setup is just safer for me, but i understand your point 🙂

pratik_asabe

gmakhs No, we always stay within 0.85, 0.60 range, and we host 17 websites on same server, in which couple of them are high traffic and others are mostly low to idle..

P.S. we did our own optimization to db (my.cnf) and overall server.. also OLS + LSCACHE + REDIS, its all combine efforts..

pratik_asabe

Vendoz Like i said, ultimately you have to play around and find what works best for you, what worked for us might not work for you or anyone else but its a starting point for you.. and yes you're absolutely right the backend operations and all can cause significant problems when spike happens.. monitor and tweak and let us know what works for you so we can all learn as well 🙂

josedieguez

it seems like we are offering too much with our plans, looking at these recommendations lol.

about last cuestion made by gmakhs

we use NPROC 50 for basic hosting, 100 for normal and 200 for high or nodeJS.

gmakhs

josedieguez Thats intresting are you using litespeed? do you have the default settings?

gmakhs

My understanding is that running the web server in native mode, runs the php under the web server and not the user container,
This allows the user to use all available CPU, I did a test with a user with 2 core CPU and he managed to use 6 , all that by php processes on a normal wordpress website using loader io and other tools
I wonder if enabling suexec and run php within users directory will solve the issue .

https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:php:which_php_setup_am_i_using

If I am right PHP external app should be added by enhance on setups, or we need a guide to set it up properly and make sure it won't be messed up on updates .

Su exec is also one of the main differences between my enhance and DA +cl server

prasad0889

gmakhs That's a good finding, and we too have come across it a few times, with mostly hacked wordpress websites using up all the CPU, the monitoring tells us, where the issue is, and we check the account for issues, but as per the enhance team with cgroups this shouldn't happen. @Adam could you please chime in?

cPFence

prasad0889

cgroups CPU limits can't be bypassed as they're enforced at the kernel level, but high server load can still occur if users are allocated too much CPU, leading to waiting tasks and contention. Other resources like disk I/O or RAM can also become bottlenecks. So, it's important to set ALL limits wisely to keep things under control.

CloudLinux simplifies this by automatically managing resource limits, but when relying solely on cgroups, you need to carefully tweak settings and optimize limits to ensure balanced performance.

« Previous Page Next Page »