PAL v1.3.4.3

Rating:        Based on 8 ratings
Reviewed:  5 reviews
Downloads: 30463
Released: Aug 29, 2008
Updated: Feb 4, 2009 by ClintH
Dev status: Stable Help Icon

Recommended Download

application, 1734K, uploaded Dec 24, 2008 - 21691 downloads

Other Available Downloads

Source Code PAL.vbs
source code, 223K, uploaded Dec 24, 2008 - 4287 downloads
Documentation IntroductionToPAL.xps
documentation, 4926K, uploaded Feb 4, 2009 - 4485 downloads

Release Notes

PAL v1.3.4.3
  • PAL.vbs update: Performance update. The PAL.vbs script was updated with a much faster counter string comparison function written by Ricardo Torre (
  • Threshold file update: The BizTalk 2006 threshold file has been updated to create a warning alert when a throttling delay of more than 2 seconds versus 5 seconds occurs and create a critical when a delay of more than 5 seconds occurs.
  • Threshold file update: The Disk Free Space for a Kernel Dump analysis has been updated to show that it is referring to a complete memory dump versus just a kernel dump. Found by Nitin Gupta (

PAL v1.3.4.2
  • Log Row Too Long: Due to the high frequency of "Log Row Too Long" errors, I have set the CSVInMaxRowSize registry key to its maximum size during setup of PAL. Performance might become slower for some users, but this will ensure better functionality for all. This error occurs when there are a large number of process counter instances in the counter log. Log Parser has difficulty with when there are too many counter instances in the log therefore by increasing its buffer to the maximum setting, I'm hoping to minimize the occurrence of these errors.
PAL v1.3.4.1
  • Threshold File Update: Removed the word, "average", from the Processor Utilization analysis because sometimes the alert will trigger on processor spikes versus averages. Thank you to Matt Reynolds for reporting this bug.
  • Threshold File Update: Added the ID Process (PID) for each of the BizTalk 2006 host instances to make it easier to identify them. Suggested by Manuel Stern and Christine Eaton. Thank you.
  • Bug Fix: The new threshold file Quick System Overview was not in the setup build and failed to make it into v1.3.4. Added to this build. Sorry.

PAL v1.3.4
  • Bug Fix: Fixed a bug where charts and threshold would not show up for analysis that really do have them defined. This was caused by the aExclusions() array not being reinitialized during each loop.
  • New Threshold File: Quick System Overview has been added as a threshold file. This threshold file is very similar to the System Overview threshold file except it does not analyze all of the processes. This is important because some perfmon logs have a very large number of processes and this causes too much overhead on Log Parser (ref: "Log row too long") and prevents it from processing. By not processing processes it makes the analysis much faster than the other threshold files and should be able to process log where other threshold files have failed.
  • Threshold File Update: Due to issues with the Microsoft Log Parser error, "Log row too long", Mike Lagase moved the threshold files back out into separate files for the Microsoft Exchange server roles in an attempt to prevent the error from occurring.

Reviews for this release

PAL helps the IT administrator to identify performance issues in a very effective way. The script driven approch makes it real easy to work with PAL.
by Apoc1970 on Feb 7, 2009 at 9:50 PM
This is an amazingly useful tool, and very easy to use.
by MitchWheat on Jan 11, 2009 at 1:36 AM
This is an essential tool that belongs in every serious in every collection of performance analysis tools. One of it's greatest features is the automation of the initial analysis, which can pinpoint key areas of concern quickly, leaving the administrator time to dig deeper into the data in a more focused manner.
by EdZ on Nov 18, 2008 at 4:39 AM
This tool allow a deeply analysis of the staus of the machine, usog automatic procedure
by Emanuele74 on Oct 4, 2008 at 10:48 PM
This tool rules. Folks genuinely like the ease of which they can decipher "what counter is off, and what should I look for"
by gwalters on Sep 10, 2008 at 4:52 PM