2

Closed

PAL v2.3 (multi-threaded version) The analysis interval is larger....

description

Facing the issue, that Pal terminates for following reason:
 
Begin: 18.5.2012 6:40:00
End: 19.5.2012 10:31:03
Samples: 4354
The command completed successfully.
Number Of Counter Instances In Perfmon Log: 1957
 
Processing: LogicalDisk Read Latency Analysis
    Time data (one time only)...Done
    Counter data for "R:"...Done
    Auto analysis interval (one time only)...Done
    Quantized index (one time only)...WARNING: The analysis interval is larg
er than the time range of the entire log.
Please use an analysis interval that is smaller than -120.004 seconds.
WARNING: Log Start Time: 05/18/2012 06:40:00.721
WARNING: Log Stop Time: 05/18/2012 06:38:00.717
WARNING: Log Length: -00:02:00.0040000
 
Why is the Stop Time behing Start time?
 
Thank you Jürgen

file attachments

Closed Jan 3, 2013 at 6:55 PM by ClintH
Fixed in PAL v2.3.3

comments

ClintH wrote Jun 1, 2012 at 8:49 PM

This is a bug with how Relog.exe is interpreting the parameters. For example, if I passed in the parameters "-b '2012-06-01 3:40:38 AM'" and "-e '2012-06-01 3:40:38 PM'" (notice the AM and PM) from PAL.ps1 into Relog.exe, then Relog would just truncate the AM and PM and it would make them the same date time. I fixed this by removing the space like this "-b '2012-06-01 3:40:38AM'" between the time and AM and this seems to work much better. I've only tested this on Windows 7 though.

I have attached an updated version of PAL.ps1 which is currently proposed as v2.3.1. Please try it and see if it resolves this issue for you.

wrote Jun 1, 2012 at 8:50 PM

wrote Aug 28, 2012 at 7:31 AM

sicklittlemonkey wrote Aug 28, 2012 at 9:00 AM

Hi Clint.

There seem to be another couple of causes of this bug, and I'm pretty sure you could fix it in your app and PowerShell script, though I haven't had the time to learn PowerShell and have a look, sorry. ; - )

The log I'm processing starts at 5:09:08 AM, and ends at 8:50:10 AM.

(1)

If I leave the defaults in the PAL wizard the log is as follows:

[...]
-BeginTime
-EndTime
[...]
Processing: Memory Available MBytes
    Time data (one time only)...Done
    Counter data for ""...Done
    Auto analysis interval (one time only)...Done
    Quantized index (one time only)...WARNING: The analysis interval is larger than the time range of the entire log. Please use an analysis interval that is smaller than -269.997 seconds.
WARNING: Log Start Time: 08/28/2012 05:09:08.764
WARNING: Log Stop Time: 08/28/2012 05:04:38.767
WARNING: Log Length: -00:04:29.9970000

The app or script should abort if it can't get the begin & end times. If in the wizard I click the checkbox "Restrict to a DateTime Range" then the following error appears at the bottom of the Date/Time Range area: "Status: An error occurred retrieving time range from counter log using Relog.exe from command line." So this case seems easy to detect.

(2)

Becuase of (1) I need to manually specify the Date/Time range, but we can't specify seconds, so I specified 5:09 AM and 8:50 AM. Look at this log for a run that didn't work:

[...]
-BeginTime 8/28/2012 5:10:11AM
-EndTime 8/28/2012 8:50:11AM
[...]
relog.exe "C:\dev\bugs\UTS\2012-8-28\VMware counters_000004.blg" -cf "C:\Users\nickw\AppData\Local\Temp{21060e1e-3cad-406e-b821-fc1735ed1892}\CounterListFilter.txt" -f csv -o "C:\Users\nickw\AppData\Local\Temp{21060e1e-3cad-406e-b821-fc1735ed1892}_FilteredPerfmonLog.csv" -y -b "8/28/2012 5:10:11AM" -e "8/28/2012 8:50:11AM"
[...]
Processing: Memory Available MBytes
    Time data (one time only)...Done
    Counter data for ""...Done
    Auto analysis interval (one time only)...Done
    Quantized index (one time only)...WARNING: The analysis interval is larger than the time range of the entire log. Please use an analysis interval that is smaller than -359.996 seconds.
WARNING: Log Start Time: 08/28/2012 05:10:38.763
WARNING: Log Stop Time: 08/28/2012 05:04:38.767
WARNING: Log Length: -00:05:59.9960000

Where did those 11 second values come from? It seems to matter, and if I choose an end time of 8:49 AM it works!

Anyway, thanks for such an awesome tool, and I hope me raising these corner cases can make it even better. Feel free to contact me if you need a .blg that has the problems I listed.

Cheers,
Nick.

ClintH wrote Aug 29, 2012 at 12:26 AM

Can you send me the counter log? I'll debug it from there.

ClintH wrote Jan 3, 2013 at 6:55 PM

I just fixed this in PAL v2.3.3. The problem is that there is a space in the path of the BLG file. This was causing problems with the processing of Relog.exe. It's fixed now and is working.

wrote Jan 3, 2013 at 6:55 PM

wrote Feb 22, 2013 at 12:46 AM

wrote May 16, 2013 at 11:56 AM