Roxen.git / server / base_server / global_variables.pike

version» Context lines:

Roxen.git/server/base_server/global_variables.pike:1013:    // since the effect of the gc is radically different now we    // intentionally use a different variable name to reset the value.    definvisvar ("mem_cache_gc", 300, TYPE_INT);       v = defvar ("mem_cache_size", 100,    LOCALE(1043, "Cache: Memory cache size"),    TYPE_INT,    LOCALE(1044, #"\   <p>Maximum size in MByte for all RAM caches taken together. This limit   covers the caches visible in the <a - href='/actions/?action=cachestatus.pike&class=status'>Cache status</a> - page.</p> + href='/actions/?action=cachestatus.pike&class=status&_roxen_wizard_id=&form._roxen_wizard_id;'>Cache status</a> page.</p>      <p>Note that there are many more things in the Roxen WebServer that   take space, including some caches that are not handled by the common   RAM cache. Also, there is various indirect memory overhead that is not   directly accounted for by the size calculations. All these taken   together means that the figure configured here cannot be mapped   straightly to the size of the Roxen process as reported by the OS. The   optimal setting here is the one that in general keeps the Roxen   process at a size that avoids swapping and leaves enough memory for   buffers and other processes that need to run at the same time (e.g.