Couple of Issues

#1
eaccelerator issue:

/usr/local/lib/php.ini

;eaccelerator
extension_dir = "/usr/local/lsws/lib"
extension="eaccelerator.so"
eaccelerator.shm_size="32"
eaccelerator.cache_dir="/dev/shm/lswseacc"
eaccelerator.enable="1"
eaccelerator.optimizer="1"
eaccelerator.check_mtime="1"
eaccelerator.debug="0"
eaccelerator.shm_max="0"
eaccelerator.shm_prune_period="0"
eaccelerator.shm_only="0"
eaccelerator.compress="1"
eaccelerator.compress_level="9"
eaccelerator.keys="shm"
eaccelerator.sessions="shm"
eaccelerator.content="shm"
eaccelerator.shm_ttl="60"
eaccelerator.allowed_admin_path = "/usr/local/apache/htdocs"

phpinfo shows eaccelerator is indeed installed. When viewing control.php after loading up many php intensive websites I show only a single script cached, control.php.

control.php shows the following:

Total memory 32.00 mb
Memory in use 165.12 kb (1%)

Free memory 31.84 mb
Cached scripts 1
Removed scripts 0

Definitely not right.

I have also tried moving cache_dir to /tmp/eaccelerator

I suspect this is related to suexec being enabled.

As a result, with dirrectory I have...
chown nobody /dev/shm/lswseacc
chmod 710 /dev/shm/lswseacc

restarted LSWS to no avail. Still stuck only caching the control.php itself.



The other issue is where are the default LiteSpeed 404, 406 and 500 files located so I can update those?


Thank you.
 

cmanns

Well-Known Member
#3
You may want to look into XCache, the performance with most scripts is fantastic and I've used it over 3+ years mostly every month besides a few times when apache mod_fcgid would cause us to use too much mem with it but you probably use litespeed like we do now, and our loads are nearly idle. vBulletin and such execute easy .05xx ms which shows saved cpu cycles & faster page delivery.
 

UWH-David

Active Member
#4
Are you using it in a shared environment with suexec? My understanding is xcache didn't work in such a scenario.


You may want to look into XCache, the performance with most scripts is fantastic and I've used it over 3+ years mostly every month besides a few times when apache mod_fcgid would cause us to use too much mem with it but you probably use litespeed like we do now, and our loads are nearly idle. vBulletin and such execute easy .05xx ms which shows saved cpu cycles & faster page delivery.
 
Top