animation log
Allows you to specify whether or not cache information is to be maintained on the physical disk.
Format:
animation log |
|---|
flex_caching = | boolean |
object_caching = | boolean |
Example:
animation log & |
|---|
flex_caching = | on & |
object_caching = | on |
Description:
Parameter | Value Type | Description |
|---|
flex_caching | Boolean | |
object_caching | Boolean | Specifies if information for rigid/non flexible bodies is to be cached |
Extended Definition:
1. By default, cache information necessary for animations containing flexible bodies is maintained on the disk in files with a .fcf extension. Adams PostProcessor can also maintain this information in physical memory, which can result in significantly less disk input/output, higher CPU utilization, and, consequently, faster performance. If you work in an environment with remote disk servers (accessed across a network), you should see a dramatic improvement in performance if you select to maintain the cache in memory. Users using local disk will see improvements on a smaller scale.
The disadvantage of memory caching is the increased process size and the risk that it will exceed your computer's physical memory. If your computer has enough physical memory, then this approach is more efficient. If your computer does not have enough physical memory, then its operating system will begin swapping and the animation performance may be worse than when using the .fcf file. We recommend that you test each model with this setting and monitor the process size using the Task Manager on Windows or the equivalent tool on Linux (for example, gmemusage -s on SGI).
Cautions:
1. If the cache is turned on, performance will be improved but will use up the computer’s physical memory.