LiteMage issues and review

Hedloff

Well-Known Member
#1
Hello,

I just tested LiteMage for a customer and the load on apachebench went down from 900ms to under 200ms. Great!

We have also added so that cache should be stored at each user home directory:

<IfModule LiteSpeed>
CacheRoot litemage_cache
</IfModule>

But none directory is created.
We are using RAMdisk for other cache, but LiteMage cache should be used for each customers account under /home/user/, but that is not working.

Currently the cache files are being stored here:
/dev/shm/storage/litemage/domain.tld
 
Last edited:

Hedloff

Well-Known Member
#2
We managed to get the cache in correct folder under /home/user/litemage_cache/ now.
Instructions you have for setup here:
https://www.litespeedtech.com/suppo...ge:installation#litespeed_web_server_settings

Did not work on our setup.
We just added a line in this file:
/usr/local/apache/conf/includes/pre_virtualhost_global.conf

<IfModule LiteSpeed>
CacheRoot litemage_cache
LSPHP_ProcessGroup on
</IfModule>

But we still have issues when customers try to flush their Magento/LiteMage cache. It's not deleted, just filling up their litemage_cache folder.
 

Michael A

Administrator
Staff member
#3
Hi Hedloff,

For the sake of efficiency, flushing the cache does not actually delete the cached files, it only marks them as expired. To keep LiteMage's cache from growing too large you will have to use the "cleanlitemage.sh" script in the 'admin/misc' directory of your LSWS installation directory. Once you find a good combination of settings that keep your cache at an acceptable size, you can include this script in a cron job to automate the process.

We have a short guide on how to use "cleanlitemage.sh" here: https://www.litespeedtech.com/suppo...itemage:administration#litemage_cache_cleanup

-Best,
Michael
 

Hedloff

Well-Known Member
#4
Thanks for the information.
I did try the script and it did delete everything in priv folder and also public folder.
But I would really like to see this script implemented automatically when customer installed the LiteMage Extension in Magento. If it created a cron job or something.
 

Hedloff

Well-Known Member
#5
Well, last night it seems like cache stopped working as site is loading slow again.
Under 24 hours LiteMage cached over 2.6GB of files.

LiteMage is not working, litemage_cache folder is growing but site is not cached. Have tried everyting (disable LiteMage, flush cache, disable standard cache etc.).
After deleting cache files in litemage_cache folder it's still empty and will not cache anything.
No files/folders are created!

I also tried updating to latest LiteMage 1.0.12, but nothing is cached....
Any idea?
 

mistwang

LiteSpeed Staff
#6
Make sure you are not running out of disk space.
can you please remove the whole litemage_cache folder instead of removing files under litemage_cache folder. then restart LSWS, see if it works or not.
 

Hedloff

Well-Known Member
#7
It's a brand new server and no issues with disk space.
Did try to remove the litemage_cache folder now. Restarted httpd and accessed the website, but still no litemage_cache folder created.
 

Hedloff

Well-Known Member
#8
I see that other accounts on the server also have the litemage_cache folder created even when they are not using LiteMage.
But when doing a locate on litemage_cache I see these also:

/home/virtfs/username/tmp/lshttpd/litemage_cache
/home/virtfs/username/tmp/lshttpd/litemage_cache/.cacheman.lock
/home/virtfs/username/tmp/lshttpd/litemage_cache/.cacheman.shm
/home/virtfs/username/var/tmp/lshttpd/litemage_cache
/home/virtfs/username/var/tmp/lshttpd/litemage_cache/.cacheman.lock
/home/virtfs/username/var/tmp/lshttpd/litemage_cache/.cacheman.shm

Could they be causing issues?
I have forced update of CageFS also, but no luck there.
 

mistwang

LiteSpeed Staff
#9
Looks like LiteMage is not enabled for that account. Make sure you account level litemage configuration is correct.
If you configured litemage with cache root /home/user/litemage_cache, you may need to create the cache root directory, and make it writeable by nobody user, otherwise there might be permission issue.
 
Top