How big are the nightly Performance Sentry data files?

You can expect data files on the order of 8-12MB daily. If you find that your daily .smf data files are significantly larger and that amount of data is causing unacceptable problems and delays in post-processing, there are several approaches that you can use to trim them back in size without sacrificing clarity and detail.

Review your Filter definitions.

The Filter definitions that you activate can have a major impact on the size of the .smf data files that you collect. If you are collecting an excessive number of process instance records, check your Process Filter settings. By raising the threshold for collecting data a little bit you might be able to reduce the amount of data in the file considerably.

If you find that it is the high volume of Object instances other than Process that is causing the problem, please contact Customer Support and send us a copy of your data file. We are always looking for ways to make the filtering process more intelligent.

Use the Summarization Utility

Running the Summarization Utility before you post process the .smf data file can reduce the amount of data to be processed significantly.  We developed the Summarization Utility because performance management and capacity planning both work off the same source data,  but at different levels of granularity. To spot performance problems and diagnose, you need detailed data. To do trend long term capacity requirements, you need summary data. Problem diagnosis normally requires recording measurement data at one minute intervals, while capacity planning trending can often work with 15, 20, 30 or 60 minute intervals. To reconcile both needs, collect detailed data for performance management, invoke the Summarization Utility at Cycle End to reduce the size of the data file, and then transmit the summarized file for post-processing.

Output files generated by the Summarization Utility conform in all respects to the original Performance Sentry data file format, except that the collection interval between data records is longer. They are managed by the same hierarchical file management parameters that control the automatic archiving and deletion of the detail files. Remember that the the Summarization Utility requires that the Data Collection Set (DCS) include the Type 5 and Type 6 Counter Type discovery records to summarize the input data correctly.

Comments are closed.