Cache

There is a performance difference between static sites and sites available from dynamic systems. The performance loss occurs because the pages are assembled at the time they are requested by the user. To improve performance, the LumisXP Server has two levels of cache for page delivery. The first is at the interface level and the second is at the page level.

Interface Cache

The service interfaces instantiated on a page are cached in memory. This cache is updated with each change in the interface or the service contents. It is typically used when the content of the pages is not altered according to the context or user accessing it. An interface that requires personalization cannot have cache at the interface level.

On a page, there can be several instances of interfaces from different services, the cache configuration is individual per instance.

Page Cache

When activated, the Portal Server keeps a copy of the page in a static HTML file and serves it in place of the dynamic one. This cache allows for performance similar to a static site.

The HTML page is updated with each change in its layout or in the content of the services that have instantiated interfaces on this page. The update is automatic and follows a publication queue. In this case, there may be a minimal delay between the change and the cache update.