Server Settings

Set caching preferences

Server Settings > Caching

 

The following table describes the caching settings. Click Submit Changes to save your changes.

 

Option

Description

Default

Maximum number of cached templates

Limits the number of templates cached. If your server has sufficient memory, you can achieve optimum performance by setting this value to the total number of ColdFusion templates in your application. ColdFusion caches templates incrementally, so specifying a high value does not automatically reduce available memory.

1024

Trusted cache

Select this option so ColdFusion uses cached application pages (templates) without first checking to see if they changed. For sites where templates are not updated during the life of the server, using this option minimizes file system overhead.

Disabled

Cache Template in Request

Inspect requested files for potential updates in the current request.

Enabled

Component Cache

Select this check box to allow ColdFusion to cache the component path resolution and not resolve it again. This setting does not require restarting the server.

Enabled

Save class files

Select this option to save to disk the class files generated by the ColdFusion bytecode compiler. Adobe recommends selecting this option for production systems; during the development phase, it is typically faster to disable this option.

Enabled

Cache web server paths
(Not enabled in the J2EE configuration)

Select this option to cache ColdFusion page paths for a single server. Deselect this option if ColdFusion connects to a web server with multiple websites or multiple virtual websites.

 

To configure this setting when using the J2EE configuration on JRun, set the cacheRealPath attribute to false for the ProxyService in the jrun.xml file.

Disabled

Maximum number of cached queries

Select this option by entering a value to limit the maximum number of cached queries that the server  maintains. Cached queries allow for retrieval of result sets from memory rather than through a database transaction. Because queries reside in memory, and query result set sizes differ, you must provide some user-imposed limit for the number of cached queries.

 

When the maximum number of cached queries is reached, the oldest query is dropped from the cache and replaced with the specified query. If you set the maximum number of cached queries to 0, query caching is unlimited.

100

Clear Template Cache Now

Empties the template cache. ColdFusion reloads templates into memory the next time they are requested and recompiles them if they have been modified.

 

Clear Component Cache Now

Clears the component cache. After the cache is cleared, ColdFusion ignores the resolved path for the components and tries resolving it again.

 

Related topic