Classic models are cached for DiveLine 7.x the same as they were for 6.x. The option for caching classic models in earlier versions is deprecated and set to default to Always.
- DivePlan-based caching optimizes the merging of MultiModels, that is, the work of matching dimension values between different models in a MultiModel DivePlan. Any user-based access control restrictions on the models get applied after the merge. Caching only optimizes the opening of the DivePlan.
- When generating a cache for a classic model, DiveLine creates two files:
- A cache information file (cinfo)—a DI object file containing the list of merged models
- The actual cache file (cac)—binary model data.
- The cache filename is a function of the resolved model names so that aliases are not saved.
- Duplicate file names are not eliminated—if one DivePlan lists a model and a second one lists that model twice, multiple caches are generated.
- DiveLine uses the list of merged models and the cache time stamp to determine the generation and usage of the cache.
- If the list of models to be merged matches that in a cinfo file, DiveLine uses the cinfo file reference to the cac file. It checks the time stamp of the cac file against that of each model. If the cac file time stamp is newer, the cac data is used to speed the model merge process. If the time stamp is older than the model file time stamps, the cache is regenerated and the cac file resaved.
- The total amount of data to cache (the merged dimension values) must be less than 2GB.
See also: Spectre Caching.