Ram disk path setting

wanah

Well-Known Member
#1
Hello,

I would like to set the new ram disk path setting but need to know what user and group to create the ram disk with, I presume it needs to be in 777 and also how much space should I allow it concidering I've got alot of ram.

How much is an overkill, 4GB, 8GB, 16GB, 32GB ? I can manage 32GB of required but would prefer to go with 8GB unless it will neever need any more than 4GB
 

NiteWave

Administrator
#2
need to know what user and group to create the ram disk with,
the user/group which litespeed process run as(though not the root litespeed process), by default it's nobody:nobody on centOS.
you can check it by
ps -ef|grep litespeed

what's the purpose you use the ram disk, cache ?

if 4GB is enough for your server, purely depending on the web application/data size/accounts on this server. it's quite normal today a web server have >=32G memory.
 

wanah

Well-Known Member
#3
Thanks I'm asking how much memory to allocate to the ram disk for the new setting.

I've got 256 GB ram, but I've got no idea how much this feature requires. I'm not sure what is written there exactly, how regularly it's cleared etc.

Just as an example here is the line I use for litespeed's gzip cache :
Code:
tmpfs           /lsgzip    tmpfs   rw,uid=99,gid=32016,size=8G,nr_inodes=10k,mode=0770    0       0
How much is recommended for the new feature thats here :

http://www.litespeedtech.com/support/forum/showthread.php?t=7291

Added a feature that moves realtime status reports to the RAM disk to avoid blocking lshttpd process in high I/O wait situations.
Thanks
 

NiteWave

Administrator
#4
I'm not sure what is written there exactly, how regularly it's cleared etc.
for lsws gzip, it'll compress static page only. 8G looks too much.
in general, you can monitor its size by
du -sh /lsgzip
after running a few days so you'll know exactly how much it needs.
you can create a cron job to clean this cache directory as well.

regarding realtime status reports, you can check
/tmp/lshttpd/.rtreport*
should be very little disk space.
 

wanah

Well-Known Member
#5
Thanks for the info :)

It's currently only using 4 x 40 k files so it's nothing at all… maybe when the server is more busy it will grow a bit. I'll create a 1GB ram disk for now.
 
Last edited:
Top