en.help.task-protocolfilecacheedit.html Maven / Gradle / Ivy
Show all versions of console-web-plugin Show documentation
To Edit File Cache Settings for a Protocol
-
In the navigation tree, expand the Configuration node.
-
Under the Configuration node, expand the Network Config node.
-
Under the Network Config node, select the Protocols node.
The Protocols page opens.
-
On the Protocols page, click the name of the protocol that you are editing.
The Edit Protocol page opens.
-
On the Edit Protocol page, click the File Cache tab.
The File Cache page opens.
-
Select the Status Enabled checkbox to enable the file cache.
This option is selected by default.
-
In the Max Age field, type the maximum age, in seconds, for a valid cache entry.
This parameter controls how long cached information is used after a file has been cached. An entry older than the maximum age is replaced by a new entry for the same file. If your content changes infrequently, increase this value for improved performance.
The optimum maximum age depends on whether existing files are modified regularly. For example, if files are modified four times a day at regular intervals, consider setting the maximum age to 21600 seconds (6 hours). Otherwise, consider setting the maximum age to the longest time for which you are willing to serve the previous version of a file after the file has been modified.
The default value is 30.
-
In the Max Cache Size field, type The maximum total size (in bytes) of the file cache on disk.
The default value is 10485760.
-
In the Max File Count field, type the maximum number of files that can be stored in the file cache.
If the value is too big, the server caches little-needed files, which wastes memory. If the value is too small, the benefit of caching is lost. Try different values of this attribute to find the optimal solution for specific applications.
The default value is 1024.
-
Click Save.
Tip:
To return to the default settings, click the Load Defaults button, then click Save.
See Also
-
-
-
-
-
-
-
-
-
-
-
Copyright © 2005, 2017, Oracle and/or its affiliates. All rights reserved. Legal Notices