Docs ModMemCache » History » Revision 10

Revision 9 (Anonymous, 2007-08-06 21:30) → Revision 10/24 (Anonymous, 2007-08-07 17:10)

 Local File Accelerating 

 Module: mod_mem_cache 

 .. meta:: 
   :keywords: lighttpd, cache 
 .. contents:: Table of Contents 

 Serving several thousands small files for lighttpd is quite challenging. Operating System has to do a lot of random access, which increase io-wait. mod_mem_cache is the plugin which stores content of files in memory for faster serving. It's more configurable than OS buffers (at least, linux buffers), in some cases yields better performance. 

 For example, you can configure it to cache files smaller than 5 kb, just cache files with a specific mime type or different strategies to free memory when the configured limit has been reached. 

 This module is a 3rd party module, is not included in the official distribution. You need to download it from here: 
  * For lighttpd 1.4.13: [ mod_mem_cache] 
  * For lighttpd 1.4.15: [] (unsupported, straight port from 1.4.13 patch) 

 '''Important''': mod_mem_cache Nod_mem_cache and mod_cml (--with-lua) doesn't play nicely together since mod_mem_cache modifies how lighttpd handles cachable items. There probably won't be a patch for this since mod_cml_lua is deprecated. 


 See [] 

    content-type arrays which want to put into memory. 

    e.g.: :: 


    Default: not set, cache all files 

    enable or disable mod_mem_cache. 

    e.g.: :: 

     mem-cache.enable = "disable" 
     $HTTP["host"] == "" { 
       mem-cache.enable = "enable" 

    Default: enable 

     maxium memory in Mbytes mod-mem-cache can use. 

     Default: 512 (means 512 ''Megabytes''). 

     maxium file size in Kbytes of single file to cache in memory. 

     Default: 512 (means 512 ''Kilobytes''). 

     number of cached memory items to remove when used memory reached maxmemory by LRU algorthim 

     Default: 200. 

     memory cache's expire time in minutes.  

     e.g.: :: 

       mem-cache.expire-time = 1440 # 1 day 

     Default: 0 (means to check file update for every request) 

     Adjusts slru threshold (against hit counter) 

     Default: 0 (disabled)  


     e.g.: :: 

       mem-compress.filetypes    = ("application/x-javascript", "text/css", "text/html", "text/javascript") # Cache javascript, css, html file in memory 
       mem-cache.max-memory = 1024 # Use 1G memory cache 
       mem-cache.max-file-size = 1024 # Cache maxium 1M-size file 

 Additional info concerning SLRU balancing 

 The SLRU has one LRU cache for the probationary segment, one for the protected segment. On the first miss an entry is added to the probationary LRU cache without any data. Only if its hit count increases over threshold it is propagated to the protected LRU cache which has real content. That way you decrease the propability that an entry is kicked out of the LRU cache as you increase the threshold for one entry getting into the cache. In practice, mem-cache.slru-thresold should adjust to archieve higher hit-rate and less memory usage