Template Caches

Caching is a means of providing more efficient retrieval of frequently accessed template-related tables. Caching duplicates the information in a temporary storage area, called a cache, on higher speed media for quicker access. Reading from a cache instead of from the database reduces bandwidth consumption, server load, and data latency (time delays), and avoids round-trip messages to and from the origin server.

Template Editor automatically caches a template whenever it is created or modified and saved. Template caching may also be done on demand and at run time. Picklists are cached as they are accessed in the system.

Cached files can be stored in a directory designated in your ngconfig.ini file or in the Template Cache Path or Template Server Cache Path in System Administrator Universal Preferences. The Template Server Cache Path works together with the Template Cache Generator.

The Template Cache Generator can be run from Template Editor or from a standalone executable file in your NextGen installation folder. When you use the Template Cache Generator, caching does not need to take place at run time unless there are changes to shared template fields or data is copied forward from one encounter to another.