adil For WooCommerce store that get 10-50 Visitor /1min, which is the least.
I see it use 5-15 nproc, and if the admin try to use the dashboard for tasks like BULK delete products or images from Library, it jumps to 30 easily. this without talking about if the site gets more visits & orders.
nproc 10 would allow for 10 concurrent PHP requests - that's dynamic requests, excluding static files or anything cached by Litespeed cache, FastCGI cache, etc. If your mean request time is 200ms then each worker can handle 5 requests per second and therefore 10 workers would theoretically handle 50 dynamic requests per second which is a huge amount of traffic for shared hosting.
Where this falls down is if the site needs to wait for something - the CPU, the disk, the database, an external API, etc. If your mean request time is 1000ms then you're only going to be able to handle 10 requests/second. If the site has max_execution_time set too high and a database call or external API is causing the request to hang, the website could easily hit the nproc limit and be unavailable for new visitors. However in a shared hosting environment this will protect your server from becoming overloaded and affecting service to other websites/customers.
For shared hosting, a low nproc/memory limit is normal. You can inform your customer that they should optimise their website or try to leverage full page caching. For VPS/dedicated hosting, set higher limits or no limits if it's the only site on the server.
