Purge Model Server Cache Impact

Writing all of the in-memory repository cache information in the SERVER_CACHE table is an input/output intensive operation. In a scenario where a single model is purged from the database will also require an almost identical task (with one less model) of all the in-memory information written to the database multiple times. To avoid this input/output intensive database write, in case of a model purge operation that does not involve purging all models, cache validity for the relevant cache in the SERVER_CACHE table is set to INVALID (value of 0). If all the models are purged, such as the products, prices, discounts, and so on, the server cache information for the corresponding model type is completely removed and any subsequence model processing updates the SERVER_CACHE table.

Note: Any model operations performed with invalid cache does not involve updating cache information in this table. This information is updated and cache validity is set to VALID (value of 1) with a subsequent application server restart as detailed in the "Repository Cache Rebuild" section in the Model Processing topic.