Proxy server: Cache management

squid.inc squidcache Proxy server: Cache management General settings /pkg_edit.php?xml=squid.xml&id=0 Upstream proxy /pkg_edit.php?xml=squid_upstream.xml&id=0 Cache management /pkg_edit.php?xml=squid_cache.xml&id=0 Access control /pkg_edit.php?xml=squid_nac.xml&id=0 Traffic management /pkg_edit.php?xml=squid_traffic.xml&id=0 Auth settings /pkg_edit.php?xml=squid_auth.xml&id=0 Local users /pkg.php?xml=squid_users.xml Hard disk cache size harddisk_cache_size This is the amount of disk space (in megabytes) to use for cached objects. 100 input Hard disk cache location harddisk_cache_location This is the directory where the cache will be stored. (note: do not end with a /). If you change this location, squid needs to make a new cache, this could take a while /var/squid/cache 60 input Memory cache size memory_cache_size This is the amount of physical RAM (in megabytes) to be used for negative cache and in-transit objects. This value should not exceed more than 50% of the installed RAM. The minimum value is 1MB. 8 input Minimum object size minimum_object_size Objects smaller than the size specified (in kilobytes) will not be saved on disk. The default value is 0, meaning there is no minimum. 0 input Maximum object size maximum_object_size Objects larger than the size specified (in kilobytes) will not be saved on disk. If you wish to increase speed more than you want to save bandwidth, this should be set to a low value. 4 input Level 1 subdirectories level1_subdirs Each level-1 directory contains 256 subdirectories, so a value of 256 level-1 directories will use a total of 65536 directories for the hard disk cache. This will significantly slow down the startup process of the proxy service, but can speed up the caching under certain conditions. 16 select Memory replacement policy memory_replacement The memory replacement policy determines which objects are purged from memory when space is needed. The default policy for memory replacement is GDSF. LRU: Last Recently Used Policy - The LRU policies keep recently referenced objects. i.e., it replaces the object that has not been accessed for the longest time. Heap GDSF: Greedy-Dual Size Frequency - The Heap GDSF policy optimizes object-hit rate by keeping smaller, popular objects in cache. It achieves a lower byte hit rate than LFUDA though, since it evicts larger (possibly popular) objects. Heap LFUDA: Least Frequently Used with Dynamic Aging - The Heap LFUDA policy keeps popular objects in cache regardless of their size and thus optimizes byte hit rate at the expense of hit rate since one large, popular object will prevent many smaller, slightly less popular objects from being cached. Heap LRU: Last Recently Used - Works like LRU, but uses a heap instead. Note: If using the LFUDA replacement policy, the value of Maximum Object Size should be increased above its default of 12KB to maximuze the potential byte hit rate improvement of LFUDA. heap GDSF select Cache replacement policy cache_replacement The cache replacement policy decides which objects will remain in cache and which objects are replaced to create space for the new objects. The default policy for cache replacement is LFUDA. Please see the type descriptions specified in the memory replacement policy for additional detail. heap LFUDA select Do not cache donotcache Enter each domain or IP address on a new line that should never be cached. textarea base64 5 50 Enable offline mode enable_offline Enable this option and the proxy server will never try to validate cached objects. The offline mode gives access to more cached information than the proposed feature would allow (stale cached versions, where the origin server should have been contacted). checkbox if($_POST['harddisk_cache_size'] != $config['installedpackages']['squidcache']['config'][0]['harddisk_cache_size']) { $needs_dash_z = true; } squid_validate_cache($_POST, &$input_errors); squid_resync(); if($needs_dash_z) squid_dash_z();