Gary, quick question...

I just followed your tutorial on eAccelerator, but I am puzzled by one line.

Change to eaccelerator.shm_size="1"

Surely, this disables the caching totally in eA??

I tried your tutorial, eventhough my PHP info is showing it as installed and so is php -v the actual /dev/ea directory never caches any files. I have got vBSEO setup on one account and that shows eAccelerator as not available.

Now, I'm puzzled..

Have you changed the line:

change this line

 

eaccelerator.cache_dir="/tmp/eaccelerator"

to

 

eaccelerator.cache_dir="/dev/ea"

and made the directory aswell as make it writable ?

 

mkdir /dev/ea

 

chmod 777 /dev/ea

Then restart LiteSpeed:

This value:

 

Change to eaccelerator.shm_size="1"

I put to this low as Litespeed can spawn upto 10 threads per cycle, And if you have alot of incoming connections this will build up your memory very fast if its on the default 16, Now there will be no performance lost setting to this value.

Thanks Gary, I must be having a blonde day! lol Forgot to Restart LiteSpeed, now I have directories and files in the /dev/ea

Much appreciated! :)

No problem my friend, I hope this works well for you.

Leave it for 24hours, Then check memory and such, You may be able to increase the output in the SHM :)

But let me know how it goes please.

Thanks.

Server is atm idling but in heavy usage memory difference is huge.

Memory usage: Apache 2.2.15

         	total   	used   	free 	shared	buffers 	cached

Mem:      	4053   	3808    	244      	0    	257   	2584

-/+ buffers/cache:    	966   	3087

Swap:     	2047     	41   	2006

LiteSpeed 4.0.17

         	total   	used   	free 	shared	buffers 	cached

Mem:      	4053   	3504    	549      	0    	257   	2635

-/+ buffers/cache:    	611   	3442

Swap:     	2047     	41   	2006

The only possablility of that is when switching to LSWS all the php processes must not have died properly causing apache and LSWB to function at the same time.

What you should do is kill all php processes / apache processes from the command line, It will not do anything just when LSWS is set then the old processes will not start and the ones that do will be just from litespeed.

If your using the WHM plugin you can do it by clicking your average server loads top right Then select kill all processes by [THIS_USER]

It just proves LSWS has better memory management than Apache, of course all processes were slayed.

So I guess by killing all php processes worked ? It would have took your swap down alot too :)

No i'm just saying that I did that when I took those stats.

Ohh, But yes LSWS does have a 30% memory loss when switching from apache.