What are the implications of changing the interval times of a TSD file?
The interval period determines how often data is collected by a SilkPerformer agent.
For example an interval of 5 seconds means that the agent queries the machine for specific measures every 5 seconds.
Changing the interval to a larger amount will create smaller TSD files because less measures are taken during a specified period. Thus disk space will be saved
The larger the interval period the less CPU resources will be needed because the agent will be running the query less often. For example if your CPU has to process at an interval of every few seconds more resources will be used but if your interval period is much larger not as much processing is required.
The longer the interval period the less stress will be placed on your CPU. The shorter the interval, the more often requests are made for data.
Using a larger interval will also create less network traffic because the TSD files being returned to the controller machine will be smaller.
The interval period should not have any effect on memory and you will not lose any accuracy of the TSD file regardless of size. However it is important to be aware that a high CPU usage could compromise the validity of the test.
Also, if using Clientside Monitoring, some load will therefore be generated on the SilkPerformer MMC controller. For more details please see
What resource overhead is incurred during SilkPerformer 2006 R2"s realtime clientside monitoring and will it skew my results?