File Cache Warm up Extension

Question

I noticed the new File Cache Warm-Up extension. While I understand the general concept of cache warming and its role in improving performance, I'd be interested in learning more about why Verint introduced this capability. What specific challenges is it intended to address, and what benefits should customers expect to see from it?

Michael Monteleone · Accepted Answer

This is primarily designed for environments using cloud storage, and it grew out of our own AWS-based hosting cluster&rsquo;s reliance on S3, where this plugin is enabled by default. Community uses several approaches to improve S3 performance as a file storage provider and avoid requiring users to wait on S3 operations, including:

CDNs for public files 
 Caching file metadata and content in-process 
 Caching file metadata and content in the distributed cache (Infra) 
 Using a combination of write-through and write-behind file caching strategies for file updates 
 Pre-warming the distributed and in-process file caches with commonly accessed files, such as theme and widget definitions, after certain operations, including startup, cache clears, and distributed cache disconnects/reconnects

These same caching optimizations benefit non-cloud storage providers as well, but to a lesser extent. By default, pre-warming is not even enabled. A customer would likely not expect to see much benefit from enabling it unless they are using a cloud provider like S3.

File Cache Warm up Extension

Top Replies