Differences

This shows you the differences between two versions of the page.

--- litespeed_wiki:config:ram_disk_path [2015/05/28 19:07]
Jackson Zhang created
+++ litespeed_wiki:config:ram_disk_path [2015/06/01 15:24] (current)
Jackson Zhang
@@ Line 3: / Line 3: @@
 [[http://www.litespeedtech.com/docs/webserver/config/tuning#ramDiskPath|RAM Disk Path]] (setting under configuration->server->tuning->RAM Disk Path. ) would help and what kind of data will be stored to RAM Disk if it is set. Actually this setting is only for LSWS real time stats data, not for swapping directory or anything else. Mitigation to your server high I/O issue may be very limited.
-General speaking, swap directory can be set to your RAM disk. PHP session path can also be set to RAM disk. These can be set explicitly through the dedicate configuration instead of from LSWS.  However, you can set [[http://www.litespeedtech.com/docs/webserver/config/tuning#gzipCacheDir|GZIP Compression Static GZIP Cache Directory]] in LSWS to RAM disk if you like.
+General speaking, LiteSpeed web server uses its own virtual memory to reduce the system memory usage. Virtual memory and disk swapping are used to store big request bodies and dynamically generated responses. [[http://litespeedtech.com/docs/webserver/config/general#swappingDir|This Swap Directory]] is different than OS swap directory  and can be set to your RAM disk through LSWS setting. While OS Swap Directory can be set on OS level.[[http://www.litespeedtech.com/docs/webserver/config/tuning#gzipCacheDir|GZIP Compression Static GZIP Cache Directory]] can also be set to RAM Disk. PHP session path can also be set to RAM disk through php.ini as well.
-Higher I/O wait is normally caused by higher disk I/O activities. There could be caused by many factors. Good practice is to identify where the disk I/O activities coming from instead of setting everything above without knowing the root cause. You may run iotop command to find out more, or do some strace on the process which generates a lot of disk I/O. Once root cause identified, RAM disk may help, though, the setting could be on your OS level instead of LiteSpeed Web Server level.
+Overall LSWS has been optimized for most of the scenarios. Occasionally, if your server is constantly dealing with dynamic content with request/response body larger than 1MB, LSWS may use temporary file to store the body data, which could increase disk I/O activities and cause higher I/O wait. However, it rarely happens.
+Higher I/O wait is normally caused by higher disk I/O activities. There could be caused by many factors. Good practice is to identify where the disk I/O activities coming from instead of setting everything above without knowing the root cause. You may run iotop command to find out more, or do some strace on the process which generates a lot of disk I/O. Once root cause identified, it may be easy to fix the problem accordingly.