Oct 7, 2011 at 3:45 PM
Edited Oct 7, 2011 at 3:52 PM
|
Has anyone else has noted that PAL 2.0.8 doesn't generate an alert when Memory:Pages/sec climbs over 1000 even when the graph clearly shows it has surpassed the threshold? Just to make sure the capture wasn't somehow misread I ran the same capture through
PAL 1.3.6.2, PAL 2.0.8 and Perfmon (Win2k3), and all three tools gave different graphs of Memory:Pages/sec.
\Memory\Pages/sec
Min Avg Max
PAL 2.0.8: 1829 3774 6016
PAL 1.3.6.2: 0 2103 10038
Perfmon W2k3: 1829 3774 6016
Graphs
(click to enlarge)
PAL 2.0.8
PAL 1.3.6.2
Perfmon Win2k3
|
|
Coordinator
Oct 14, 2011 at 12:34 AM
|
PAL v1.x only charted the average values of each time slice (PAL breaks the log up into 30 equal time slices when processing a counter log). PAL v2.x plots *all* of the data points found in the log to the chart. In all versions of PAL, I use Relog.exe (part
of the operating system) to convert the binary log to a CSV file. During this conversion Relog sometimes doesn't have enough "buckets" to do a completely 1:1 for all of the data points. In any case, the chart between Perfmon Win2k3 and PAL 2.0.8 seem very
close with the exception of the first data point on the PAL 2.0.8 chart.
|
|