LiteSpeed number of Workers
-
First question is how may CPU cores do you have have? You don't want more workers that cores and you don't want to "use" all your cores, because you still need cores for PHP and MySQL. Is it faster than Apache and Nginx, you can look at benchmarks etc. and decide. Is it a while lot easier /quicker to install and tweak (which you prob. won't have to do) yes. From our experience the combination of LSWS and the LSWS Cache for WP makes customers happy. 0 -
First question is how may CPU cores do you have have? You don't want more workers that cores and you don't want to "use" all your cores, because you still need cores for PHP and MySQL. Is it faster than Apache and Nginx, you can look at benchmarks etc. and decide. Is it a while lot easier /quicker to install and tweak (which you prob. won't have to do) yes. From our experience the combination of LSWS and the LSWS Cache for WP makes customers happy.
Hi, Thank you very much. We will buy new server and we are checking this processors: Intel 2x Xeon E5-2630v3 - 16c/32t - 2.4 GHz/3.2 GHz Intel Xeon-D 2141I - 8c/16t - 2.2 GHz/3 GHz Intel Xeon-E 2288G - 8c/16t - 3.7 GHz/5 GHz Intel Xeon E5-1650v4 - 6c/ 12t - 3.6 GHz/ 4 GHz We will host 300 cPanel accounts with normal wordpress. Can you recommend me best processor for this requeriments and number of workers in litespeed?. If you know best OVH server for 300 cPanel accounts link me please. Thank you again.0 -
For 300 accounts, I'd just start out with the 2 worker license (as I believe that will give you the WordPress cache option). If your not happy with that then go to the 4 or larger. The number of sites is not really a good indicator vs. the traffic / complexity of the site. 0 -
For 300 accounts, I'd just start out with the 2 worker license (as I believe that will give you the WordPress cache option). If your not happy with that then go to the 4 or larger. The number of sites is not really a good indicator vs. the traffic / complexity of the site.
Thank you very much for all info.0 -
Hello, Glad to see you were able to get the information you were looking for, please let us know if you have any further questions or concerns. 0 -
You should consider the instant php query instead of the number of sites. If all 300 websites are not running intensive php queries, 1 worker license is sufficient. If websites have very intense php queries, you can choose 2 workers for 12 cores, 4 workers for 16 cores and above. The worker determines how many cores the main litespeed processes will run on, the main processes execute the lsapi processes and bifurcation processes, so the choice should be made based on the instantaneous processing density on the server and how many core processors the server has. 0 -
You should consider the instant php query instead of the number of sites. If all 300 websites are not running intensive php queries, 1 worker license is sufficient. If websites have very intense php queries, you can choose 2 workers for 12 cores, 4 workers for 16 cores and above. The worker determines how many cores the main litespeed processes will run on, the main processes execute the lsapi processes and bifurcation processes, so the choice should be made based on the instantaneous processing density on the server and how many core processors the server has.
Oh, I did not know that. I think i will buy 1 worker and test speed, if need more will change to next plan. Thank you very much.0 -
I have same problem deciding about amount of workers. Server CPU - AMD EPYC 48 cores (2 logical cores per physical - 96 total). Most of website pages are cached as pure HTML/CSS and no PHP/database involved, until member login (but that is less than 1% of visitors). Daily visitors increase expected in time period 8am-8pm (12 hours): 1 - 2.5 million Was adviced about 2 workers plan, but I think that is too less workers. I may be wrong. How many is best estimate based on our server and expected traffic increase (as stated above). 0 -
I have same problem deciding about amount of workers. Server CPU - AMD EPYC 48 cores (2 logical cores per physical - 96 total). Most of website pages are cached as pure HTML/CSS and no PHP/database involved, until member login (but that is less than 1% of visitors). Daily visitors increase expected in time period 8am-8pm (12 hours): 1 - 2.5 million Was adviced about 2 workers plan, but I think that is too less workers. I may be wrong. How many is best estimate based on our server and expected traffic increase (as stated above).
If there are websites with html content without database, 1 worker will suffice. If 1 worker is not enough, there is always a chance to upgrade to 2 workers. It also has a trial license 2 worker feature, you can test it for 14 days. *** How do I know if it's enough? There is a litespeed document for this. A top command will reveal important information about how different processes are using server resources. (LSWS's process is called lshttpd.) A couple of these outputs are useful for determining if the current LSWS installation could benefit from access to more cores:- %CPU - Generally LSWS's CPU usage is low. If LSWS's CPU usage starts climbing, and especially if it climbs while the overall load is low, it can indicate that LSWS is hitting a bottleneck and would benefit from access to more cores.
- %wa - High I/O wait can also be an indicator that LSWS needs more worker processes (and thus access to more cores).
0 -
In this server, how many workers do you recommend for 2000 cPanels? Dual E5-2699v4 (44 cores 88 threads) 256GB RAM 2x 4TB SSD + 16TB HDD 25TB bw @ 1Gbps 0 -
In this server, how many workers do you recommend for 2000 cPanels? Dual E5-2699v4 (44 cores 88 threads) 256GB RAM 2x 4TB SSD + 16TB HDD 25TB bw @ 1Gbps
4 workers are enough.0 -
Is 1 worker enough for this type of server: 2 x Intel E5, 8 Core CPU (32 threads) server with 96 GB of RAM, cPanel and CloudLinux with up to 200 accounts. 0 -
maybe i'm replying to a very old thread (jan 2023 last reply). but this thread comes up on top in a google search related to litespeed workers and their licenses. Wanted to share my experience. Servers with different panels, and between 200-600 cpanel accounts (1-2 thousand domains) on very powerful servers 20.000-30.000-40.000 cpubenchmark, the litespeed 1 worker license have been enough on all cases except one. When there is some DDoS is the only time i see the lshtppd process raise to 80-90% CPU, and indeed, everything gets slower, with plenty of ram, cpu, and port speed available, still, websites are failing to load. An upgrade there to the 2 worker license, makes every website to load fast again (With the DDoS ongoing, and trying to mitigate it) According to the stats the DDoS is between 40.000 and 120.000 requests per second, (not enough to saturate network port or entire CPU, but enough to fully utilize 1 worker of litespeed). I guess that's related to their own explanation of what the worker do: " HTTPS traffic from static contents. " (and more stuff) - To summarize: I have seen 1 worker license to be enough in dozens of servers, with many clients on them doing a TOP command, you can see CPU usage of the lshttpd process, if it's low (lower than 50% they say) you are perfectly fine with 1 worker, it doesn't matter if you have 24-32-48-96 cores. Avoid paying extra :) 0 -
What if the "top" command on my Ryzen 9950X (16 cores) server looks like this, with Litespeed trial license (which has 2 workers):
I see it jump over 60-70% at time, but those seem to be spikes and then it drops down to regular levels, and it's a constant rollercoaster in doing that.
I was considering a paid 2 workers license but if 1 worker can handle this easily, I'd rather stick with that instead.
0 -
There is a point you are missing.
The important thing is the use of the lshttpd/litespeed process. The lsphp process refers to the php-side usage of the sites, while the worker processes are lshttpd or litespeed processes. If your lsphp processes consume too much and high CPU, it indicates that there is a problem with your software's php queries. Before increasing the number of Litespeed workers, I recommend that you check the php queries of the site that creates excessive lsphp processes and take a look at cache applications.
Good luck.
0
Please sign in to leave a comment.
Comments
15 comments