However, in a few cases, it may be advantageous to do so. For example, if you are reading a live data feed into your program, it is probably not necessary to cache the downstream outputs. You can change how and if the executive caches intermediate output values by opening the Configuration dialog box of a module and changing the option menu to the right of each output. You can also choose Output Cacheability from the Edit menu of the VPE, and set the cacheability of a group of modules, show the cacheability of a group of modules, or ask Data Explorer to use a heuristic to automatically optimize the caching for the current visual program. Note that if you do this, however, if you need to change the isosurface value, the data file will need to be reimported, slowing execution.
Some modules use the caching system to cache their own data.
The Display and Image tools are such tools. When using software rendering, they cache the images they display in the X windows. This is an optimization that can be seen when using the Sequencer. You can observe this effect by running the example program MovingCamera.net with software rendering. Most of the time this caching behavior is desirable, but in some cases it is better turned off.