Search results

http://www.litespeedtech.com/docs/webserver/config/tuning/#maxReqBodySize

All user's PHP script runs as its own user id, looks normal to me.

df shows that you already have it. check /etc/fstab for configuration.

set eaccelerator.cache_dir="/dev/shm/eaccelerator" Already did that on that server, load drop to 4-6 now.

looks good to me.

use a bit more CPU cycles.

We will see what we can do. usually, the vhost is named before knowing it is a SSL site or not.

You probably do not want to ScriptAlias for '/'. You can use "AddHandler cgi-script .pl .cgi ...". In other words, do whatever you need to do like with Apache.

Upgrade to the latest release and use some advice in http://www.litespeedtech.com/support/forum/showthread.php?t=2814

always check the php.ini path in a phpinfo() page. Do not remove other php.ini file, they wont interfere with your PHP, but if removed, some LSWS functions may break.

Maybe you have too many running PHP processes, for shared hosting using PHP suEXEC, try set "Max Idle time" http://www.litespeedtech.com/docs/webserver/config/extapps/#extMaxIdleTime of lsphp5 external app between "5"-"10" seconds. Also try the trick of eaccelerator using /dev/shm. more...

You need to check why the request takes so long, usually, it is a PHP/MySQL issue. Also, try our 4.0.1 release package see if it helps or not. Just change the version number in the download link to get it.

No need to increase it or let it cache more pages in memory, as the disk cache is actually in memory, also PHP process will start/stop more frequently in PHP suEXEC mode for shared hosting. As long as PHP process can grab a copy of parsed PHP opcode from memory disk, it is fine.

Yes, that's true that it will cause high I/O wait if you use /tmp/eaccelerator/ as the storage. However, using /dev/shm/ is more like using a memory disk, which is lightening fast without increasing I/O wait.

If you got some spare memory in your server not being actively used, there is one tip to improve PHP and overall server performance. :) Requirements: * there are enough free memory to spare. * /dev/shm/ should be mounted as tmpfs. Install eaccelerator with PHP suEXEC, set disk cache storage...

For the mod_security rule, are you using 4.0 enterprise? Have you tried the rule from httpd.conf instead of .htaccess?

AIO support has been added to our 4.1b1 release, you can give it preview, just change the version number in the download link to get it. This build only use AIO, tried it on a server with high disk I/O. High I/O wait should not be an issue with it. We already got some positive feedbacks for...

LiteSpeed does not support SetEnvIf... and Deny from env=..., you should switch to a pure rewrite rule based solution. it should be more efficient because there is no need to set the "env=blocked_apps".

Please try 4.0.1 release package, just change the version number in the download link. Fixed a bug that affect some plesk user, maybe related.

4.0 is the latest.