Differences

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

--- litespeed_wiki:config:ram_disk_path [2015/05/29 16:31]
Jackson Zhang
+++ 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, [[http://litespeedtech.com/docs/webserver/config/general#swappingDir|Swap Directory]] can be set to your RAM disk. [[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.
+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.
 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.