Macromedia coldfusion mx 61 Handbuch
Server Settings section
19
Caching page
The Caching page of the Administrator contains configuration options that you can set or enable
to cache templates, queries, and data sources
to cache templates, queries, and data sources
.
These options can significantly affect server
performance. The following table describes the settings:
Missing Template Handler
Specify a page to execute when ColdFusion MX cannot find a
requested page. This specification is relative to the web root.
If the user is running Internet Explorer with "Show Friendly HTTP error
messages" enabled in advanced settings (the default), Internet
Explorer will only display this page if it contains more than 512 bytes.
requested page. This specification is relative to the web root.
If the user is running Internet Explorer with "Show Friendly HTTP error
messages" enabled in advanced settings (the default), Internet
Explorer will only display this page if it contains more than 512 bytes.
Site-wide Error Handler
Specify a page to execute when ColdFusion MX encounters an error
while processing a request. This specification is relative to the web
root. If the user is running Internet Explorer with "Show Friendly HTTP
error messages" enabled in advanced settings (the default), Internet
Explorer will only display this page if it contains more than 512 bytes.
while processing a request. This specification is relative to the web
root. If the user is running Internet Explorer with "Show Friendly HTTP
error messages" enabled in advanced settings (the default), Internet
Explorer will only display this page if it contains more than 512 bytes.
Setting
Description
Template cache size
(number of templates)
(number of templates)
Enable this option to limit the memory reserved for template caching.
For best performance, set this to a value that is large enough to contain
your application’s commonly accessed ColdFusion pages, yet small
enough to avoid excessive reloading. You can experiment with a range
of values on your development server; a suitable starting point is one
page per MB of JVM size.
For best performance, set this to a value that is large enough to contain
your application’s commonly accessed ColdFusion pages, yet small
enough to avoid excessive reloading. You can experiment with a range
of values on your development server; a suitable starting point is one
page per MB of JVM size.
Trusted cache
Enable this option if you want ColdFusion MX to use cached templates
without checking whether they changed. For sites that are not updated
frequently, using this option minimizes file system overhead.
without checking whether they changed. For sites that are not updated
frequently, using this option minimizes file system overhead.
Save Class Files
Select this option to save to disk the class files generated by the
ColdFusion bytecode compiler. During the development phase, it is
typically faster to disable this option.
ColdFusion bytecode compiler. During the development phase, it is
typically faster to disable this option.
Cache web server paths
(Server configuration only)
(Server configuration only)
Select this option to cache ColdFusion page paths for a single server.
Deselect this option if ColdFusion MX connects to a web server with
multiple websites or multiple virtual websites.
Deselect this option if ColdFusion MX connects to a web server with
multiple websites or multiple virtual websites.
Limit the maximum number
of cached queries on the
server to [n] queries
of cached queries on the
server to [n] queries
Enable this option by entering a value to limit the maximum number of
cached queries that the server maintains. Cached queries allow
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 a limit for the number of cached queries.
You enable cached queries with the
cached queries that the server maintains. Cached queries allow
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 a limit for the number of cached queries.
You enable cached queries with the
cachedwithin
or
cachedafter
attributes of the
cfquery
tag.
Setting
Description