Why does Rember eat up so much of the processor's available cycles sometimes, and not at others?

Question:

Why does Rember eat up so much of the processor's available cycles sometimes, and not at others?

Answer:

When the memory tests are running, the Rember program is continuously logging, and (if chosen) filtering "garbage" information (eg. command line progress indicators). This cuts down on processor and memory hogging by Rember. When using this program to test very small amounts of memory (example: 1MB), it will not be efficient. When using the "All" option, this is alleviated. Leaving the "Log" tab selected seems to be the most efficient.