T
TomM
I'm trying to pinpoint some performance issues we are a having whereby PC’s
start running slowly and grinding to a halt, at approximately the same time
as the AV update window. I suspect that memory usage is an issue and that
the PC's may be heavily paging leading to the slowdown. I am trying to find
out why this is happening.
I have created a Performance Monitor log to include the following counters
"\Memory\Committed Bytes"
"\Memory\Pages Output/sec"
"\Memory\Pages/sec"
"\Process(FrameworkService)\Page File Bytes"
"\Process(FrameworkService Bytes Peak"
"\Processor{_Total}\%Processor Time"
The trouble is that having gathered the counters I'm having trouble actually
interpreting them.
The sample window is 2 hrs, to try and get a before and after understanding
of what is happening
I think, but am open to correction, that the 3 main counters which I should
be interested in are
\Memory\Committed Bytes
Memory\Pages/sec"
\Process(FrameworkService\Page File Bytes Peak
FrameworkService is a component of the McAfee ePo suite
I’d like to be able to show you the graphical representation, but in summary
this is what I’m seeing
\Memory\Committed Bytes is showing at maximum 100 on the scale for the
duration of the sample
\Memory\Pages/sec – peaking every few minutes to 80, 90, 95 on the scale for
the duration of the observation, with a sharp flurry of high activity
directly after the time when the FrameworkService shows a rise
\Process(FrameworkService\Page File Bytes Peak – trundles along happily at
around 20 on the graph, rises sharply to 100 on the scale, drops back and
rises almost immediately. It them flatlines and stays at 100 on the scale
until the end of the sample
I haven’t mentioned installed RAM, or the actual figures from the sample, as
the pattern appears to be the same on PC’s with 1 GB and 2GB. I can give
figures if it helps, but I think pattern is relevant
From my limited explanation, is anyone able to help me interpret this
behaviour.
Why is Memory committed Bytes constant at 100 on the scale
Why is the FrameworkService flatlining ?, what does this mean, and what
would be the results of this on PC behaviour
Thanks
start running slowly and grinding to a halt, at approximately the same time
as the AV update window. I suspect that memory usage is an issue and that
the PC's may be heavily paging leading to the slowdown. I am trying to find
out why this is happening.
I have created a Performance Monitor log to include the following counters
"\Memory\Committed Bytes"
"\Memory\Pages Output/sec"
"\Memory\Pages/sec"
"\Process(FrameworkService)\Page File Bytes"
"\Process(FrameworkService Bytes Peak"
"\Processor{_Total}\%Processor Time"
The trouble is that having gathered the counters I'm having trouble actually
interpreting them.
The sample window is 2 hrs, to try and get a before and after understanding
of what is happening
I think, but am open to correction, that the 3 main counters which I should
be interested in are
\Memory\Committed Bytes
Memory\Pages/sec"
\Process(FrameworkService\Page File Bytes Peak
FrameworkService is a component of the McAfee ePo suite
I’d like to be able to show you the graphical representation, but in summary
this is what I’m seeing
\Memory\Committed Bytes is showing at maximum 100 on the scale for the
duration of the sample
\Memory\Pages/sec – peaking every few minutes to 80, 90, 95 on the scale for
the duration of the observation, with a sharp flurry of high activity
directly after the time when the FrameworkService shows a rise
\Process(FrameworkService\Page File Bytes Peak – trundles along happily at
around 20 on the graph, rises sharply to 100 on the scale, drops back and
rises almost immediately. It them flatlines and stays at 100 on the scale
until the end of the sample
I haven’t mentioned installed RAM, or the actual figures from the sample, as
the pattern appears to be the same on PC’s with 1 GB and 2GB. I can give
figures if it helps, but I think pattern is relevant
From my limited explanation, is anyone able to help me interpret this
behaviour.
Why is Memory committed Bytes constant at 100 on the scale
Why is the FrameworkService flatlining ?, what does this mean, and what
would be the results of this on PC behaviour
Thanks