Proccess limit
- Thread starter Jetro
- Start date
3100 is calcuated from the "instances" of lshphp external application.
CGI Reource limit will apply to all external applictions, if it has not been overriden in the external application configuration at the buttom of external application.
Have 1000 lsphp external application is too much for most setup, may not help the performance at all.
CGI Reource limit will apply to all external applictions, if it has not been overriden in the external application configuration at the buttom of external application.
Have 1000 lsphp external application is too much for most setup, may not help the performance at all.
I changed max connections, because in my forum some of users talked to me that quoting posts is not possible, because it showing error 503 or Server Temporary busy... But server is not overloaded (server load ~1, other pages loading fast) :|
What should i change?
Actually i made these changes:
http://thecrims.org/1.png
http://thecrims.org/2.png
http://thecrims.org/3.png
What should i change?
Actually i made these changes:
http://thecrims.org/1.png
http://thecrims.org/2.png
http://thecrims.org/3.png
For your LSAPI config, having "Max Connections" and "Instance" values of "500" is overkill if most of your php scripts connects to a db.
To best judge what you ready need, check real-time stats during the peak hours of your forum and see how many are really in use.
More php processes does not equal to faster website because at the end, 500 concurrent php processes would need 500 concurrent mysql threads which is a load killer in it's own right. We have done some benchmarks and lsapi php values of 20 can be enough for a lot of websites provided the code is clean and mysql is humming along.
Try Max connections and instance value of "60" which should be more than enough.
As for the problem in question of 503 errors or temp busy, that's definitely a problem but appears unrelated to the config in quesiton, at least when I check the throttle values which shouldn't kick into effect.
Have you been able to reproduce the problem yourself?
The only thing I can think of right now based on info is that the throttle is kicking in. Try this. Find the forum user that is having this problem, have them reproduce it on the spot, than set the throttle values to 0/disable, restart lsws, then ask them to reproduce the problem once more.
To best judge what you ready need, check real-time stats during the peak hours of your forum and see how many are really in use.
More php processes does not equal to faster website because at the end, 500 concurrent php processes would need 500 concurrent mysql threads which is a load killer in it's own right. We have done some benchmarks and lsapi php values of 20 can be enough for a lot of websites provided the code is clean and mysql is humming along.
Try Max connections and instance value of "60" which should be more than enough.
As for the problem in question of 503 errors or temp busy, that's definitely a problem but appears unrelated to the config in quesiton, at least when I check the throttle values which shouldn't kick into effect.
Have you been able to reproduce the problem yourself?
The only thing I can think of right now based on info is that the throttle is kicking in. Try this. Find the forum user that is having this problem, have them reproduce it on the spot, than set the throttle values to 0/disable, restart lsws, then ask them to reproduce the problem once more.
Jetro,
The "Process Soft/Hard Limit" in the first screen shot is too small comparing to the value of "instances". Anyway, LSWS will increase it automatically as you have seen.
As to the 503 error, it is a PHP problem I believe, most likely PHP process had crashed, consider to build your own PHP binary with all required PHP modules.
The "Process Soft/Hard Limit" in the first screen shot is too small comparing to the value of "instances". Anyway, LSWS will increase it automatically as you have seen.
As to the 503 error, it is a PHP problem I believe, most likely PHP process had crashed, consider to build your own PHP binary with all required PHP modules.