cache - Manage the persistent cache memory
cache object [<min-size> <max-size>]
cache bigobject [off | on <min-size> <max-size>]
cache clear [report | force]
cache loadurl <url>
cache report [size | rsize | bigsize | meanobject | used | rused | hit]
The first usage form is used to modify the maximum cached object size in the persistent memory. Higher values save more bandwidth but may rapidly saturate the persistent cache memory. Lower values cache smaller objects and therefore increase performance. The size is specified in kilobytes.
The minimum size for cached object should be greater than or equal to 0 KB and less than or equal to the configured maximum size. The maximum size for cached object should be greater than or equal to 1024 KB and less than or equal to 262144 KB (256 MB). We suggest leaving these limits at their default values that are 1 KB for the minimum and 51200 KB (50 megabytes) for the maximum.
Objects smaller than or greater than those limits are not cached unless you activate the caching for very big objects. When this type of caching is activated the system reserves an area on the persistent cache to store objects bigger than the upper limit for common objects. This feature allows you to cache very big objects like smartphone OS without the disadvantage of having your total cache saturated by very big objects.
The third usage form allows you to activate or deactivate the caching of very big objects. To activate this type of caching use the keyword on followed by the minim and maximum sizes for very big objects expressed in KB. The given minimum size should be greater or equal to the maximum object size for common objects and lesser than or equal to the size of the area reserved on the persistent cache for very big objects. To deactivate it, use the keyword off. When the caching for very big objects is deactivated, the cache is totally used to store common objects.
The size of the area reserved on the persistent cache for very big objects varies depending on the size of your hard drive(s) and other parameters given during the installation (the fifth usage form described later allows you to get this size).
In some circumstances you may need to clear the entire persistent cache. For instance if the antivirus mode is activated but the related service couldn’t start (because the appliance was not connected to the Internet and the antivirus updater couldn’t start), the cache could become infected by a virus. In this case it is highly recommended to clear the cache.
The third usage form allows you to clear the entire persistent Web cache.
The fourth usage form is used to force the system to reload a given URL. A valid URL value must be in the form:
<protocole>://<domainname>[/<path>] in which <protocole> is http, https ftp. See the command domainname for a valid domain name format. The last optional part <path>, is a path to a regular filename on the remote server.
This command is useful for automating the loading of specific URLs using the ssh programmed command and a remote task scheduler.
The third usage form allows you to clear the entire persistent Web cache. When this command is invoked, the user is invited to confirm the clearing execution. The optional argument force, allows you to bypass this confirmation. The optional argument report, allows you to display a system report of the last cache clear command. Clearing operation is an asynchronous command and is executed in background. Note that you have to wait for the termination of other asynchronous commands before running this command.
The fifth usage form allows you to display a report on the cache size and activity. The keyword size displays the total cache capacity in Kilo Byte while the keyword used displays the percentage of the main cache filled by Web objects. The keyword bigsize displays the cache size for big objects. The keyword meanobject displays the mean object size in the persistent cache. The keyword hit displays the main cache usage. It expresses how much data and requests are retrieved from the main cache compared to all data and requests passing through the system since the last cache initialization (or clearing).
In some particular configurations, reverse websites use a cache space other than the main cache space. This cache space is called the rWeb cache and should have been reserved during the appliance installation. The rWeb cache is activated in one of the following configurations:
* The WAF mode is activated.
* At least one rWeb site uses a sticky load balancing over more than one backend Web server.
* At least one rWeb site uses a load balancing method other than the round robin over more than one backend Web server.
Keywords rsize and rused display respectively the rWeb cache size and the the percentage of the rWeb cache filled by Web objects. Without any keyword, the command cache report displays all these values. The limitation is that the caching of very big objects is not possible in those configuration for reverse websites.
apply (1) admin (1)
CacheGuard Technologies Ltd <www.cacheguard.com>
Send bug reports or comments to the above author.
Copyright (C) 2009-2018 CacheGuard - All rights reserved