Largest Performance Monitor Logfile (.blg) PAL can process?

Sep 12, 2013 at 6:50 PM
What is the largest Performance Monitor Logfile that PAL can process successfully? Is there a limit in the application or is it dependent on the underlying hardware? (or a bit of both?)

We can process a 1.2GB File in approx two hours on a 2 Socket 12 Core System with 16GB RAM).

We are currently trying to process a 4.0GB file on the same system and it appears that it will take approximately 12 hours.

The resources on the server were definitely taxed, ~90% CPU across all cores and !12-15GB RAM.


Sep 17, 2013 at 7:05 AM
There is no limit that I know of for PAL other than the system hardware and operating system limitations. When working with very large counter logs, consider using the Relog.exe command-line tool built into the operating system to make the counter log smaller. Relog can filter the 4 GB file to just certain counters, time ranges, or every nth value. Once reduced, the PAL tool should be able to get through the counter log faster. Please keep in mind that already PAL uses Relog to reduce the counter log into a smaller one by filtering it down to only the counters that are in the threshold files active in the analysis.