PAL running for hours with html file at 0 bytes


Hi there,

I seem to be having some trouble using the PAL tool. I was running it against some logs from SQL 2000 on a Windows Server 2003 machine using version 2.3.3 and it was maxing out the CPU for more than 30 hours but producing no output. Input blg files were no more than 1.5GB in total. I then decided to run it on another server with multiple cores but it's only running 2.3.2 and I can't change that. (Enterprise environment, can't change stuff without multiple change records) It is no longer maxing out the CPU although it using nearly 2.5GB of memory. I am just worried about leaving this runnign over night again to find it's just done nothing again.

File: C:\Documents and Settings\XXXXXXXXXX\Local Settings\Temp{526f1179-52
Begin: 25/2/2013 13:42:31
End: 13/3/2013 15:28:33
Samples: 92584
The command completed successfully.
All counter stats is set to true. Loading all counters in perfmon log into the t
hreshold file as new analyses. This may take several minutes.
Getting the counter list from the perfmon log...Getting the counter list from th
e perfmon log...
relog.exe "X:\XXXXXXXXXXXXXX\<SERVERNAME>\PAL_Microsoft_SQL_Server_2005_2008
v1.1.4.1_000003.blg" -q -o "C:\Documents and Settings\XXXXXXXXXXXXX\Local Settings\
Input ---------------- File(s): X:\XXXXXXXXXXXX\<SERVERNAME>\PAL_Micr
osoft_SQL_Server_2005_2008 v1.1.4.1_000003.blg (Binary) Begin: 25/2/2013 13:
42:31 End: 13/3/2013 15:28:33 Samples: 92584 The command completed successfully.
Getting the counter list from the perfmon log...Done!
Importing the counter list as new threshold analysesDone
Number Of Counter Instances In Perfmon Log: 445

Processing: Process % Privileged Time
    Time data (one time only)...Done
    Counter data for "sqlservr"...Done
    Quantized index (one time only)...Done
    Quantized time (one time only)...Done
And from here nothing else happens. Any suggestions? The CPU and memory usage fluctuate suggesting that something is being done but after 7 hours so far today I have no idea whether to cancel it or not.
Closed Oct 3, 2013 at 5:52 PM by ClintH


Hooksie wrote Mar 28, 2013 at 1:37 PM

Scrap that, found the problem. I'd stupidly set the time interval to the same time interval that I took the perfmon logs on i.e. 15 seconds. Left it at auto and it worked fine. I'll leave this up here in case anyone else has the same issue.

ClintH wrote Apr 2, 2013 at 5:00 AM

Good to hear that you got it working. 90,000 samples is an extremely large counter log. Consider using the Relog.exe command in the operating system to reduce the size.