Usage Monitor Help: Options
Four options are available to help you affect performance and the volume of log information collected which may be of help when resolving configuration problems.
Choose whether to write detailed logging to the event log
The utility writes information about its activity to the an Event Log source called Monitor Utility (Lyquidity). You can see this information by using the Windows event log viewer. Sometimes it may not be clear why files and folders are being monitored or not and enabling detailed logging may be of help to explain the reason.
Choose how aggressively the utility should use CPU time
The utility allows you to influence how much of the CPU the utility should consume. The options are from Aggressive, Normal, Passive and Docile. On any machine running multiple services and applications there is a balance to be struck between how much CPU time one application takes in relation to other applications and whether an application has enough CPU to complete its tasks.
Normally this is not an issue for the monitor utility which will be able to cope even on the Docile setting, especially if it is monitoring files and folders on other machines over the network as the speed of the network will be the limiting factor. However if the utility is used on a fileserver and is monitoring folders containing hundreds of thousands of workbooks of a large corporation where many of the documents are constantly changing then a higher setting may be required for it to keep up with the number of operating system event messages it will receive.
Choose whether the utility should 'find files'
When the utility is started it can be instructed to find and catalog all the files in folders that are being monitored.
Control how aggressively the utility should free used memory
All applications use and release memory. Because memory is used little bits at a time, it gradually fragments over the lifetime of an application. But it is expensive in CPU terms to constantly defragment memory as all running applications must be temporarily suspended while memory is moved around. However the utility allows you to insist that memory is defragmented.
You should use this option only if you find the memory used by the utility, as shown in the task manager for instance, is growing to be a substantial percentage of the available RAM and does not reduce automatically.
Options control how the service will operate
