track.performance: Performance tuning with track.
Description
Performance tuning with track involves trading off memory use for
faster access times to objects. Access time is fastest when all
objects are cached in memory, but memory can be exhausted if this is
done. Memory use is minimized when objects are not cached in memory
at all, but then a file must be read or written each time an object is
referenced, and the whole file must be read or written even if only a
small part of the object is actually used or changed.
The default mode of operation of track balances memory use and
access times by keeping objects in memory for the duration of a
top-level task, and flushing them out at the end of the task.
Three options (see track.options) control performance:
: TRUE/FALSE should variables be cached at all?
- cachePolicy
: tltPurge/none higher level
policy for maintaining cache
- writeToDisk
: TRUE/FALSE should objects be
written after a change?itemize
- cache=TRUE, cachePolicy="tltPurge", writeToDisk=TRUE
item
- cache=TRUE, cachePolicy="none", writeToDisk=TRUE
- cache=TRUE, cachePolicy="none", writeToDisk=FALSE
- cache=FALSE, cachePolicy="none", writeToDisk=TRUE
code
writeToDisk=TRUE