Re: Excessive Paging


Thanks Gerry, This helped but didn't solve the problem. When I let Xp
manage the file,
it started snagging file space and seems to have topped out at about
760M. I haven't
noticed an increase in peformance yet however, but I'm sure it's a step
in the right
direction

Thanks!
Ray


Gerry Cornell wrote:
Ray

Your pagefile setting is too low.
http://aumha.org/win5/a/xpvm.htm

--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~




Ray wrote:
Thanks Earl, I understand that. Are you saying that 30-50 pages/sec
is normal with 392M memory, 160M of available memory and a max
commit charge of 170M? Perhaps I'm I'm not taking into consideration
the cache/available memory relationship and expecting too much from
memory utilization and this is just normal? Perhaps I've just
crossed
over the commit level far enough to start thrashing and a memory
upgrade would be in order?

I've been through HiJackThis and SpyBot which didn't turn up
turning up anything interesting and am running AdAware at
the moment (and for many moments to come ;-p Boot times on
this machine have gone from an (albeit slow) couple of minutes
(from power on, through logon to the desktop) to about 10 minutes.
So, either something new is running on this system or something
is failing.

If there is a problem with what is running, it must be loading
at boot time. I've been trying to go through the running process
list to determine if there is something there that isn't right but
it takes time to track each process down.

I've also been through the services list and haven't found anything
out of the ordinary there either although I haven't checked each
one individually yet (hijack this should have caught anything
interesting here).

One other thing that I've noticed that I can't seem to reconcile
is why some system devices, in particular, SystemDevices->
DirectMemoryAccessController are indicating that there is no
device driver installed, the device enabled and yet the driver
tab shows a driver driver info. I ran sfc against the system but
that just quietly exited when done - does it show something
if it made changes?

Thanks,
Ray


Earl Grey wrote:
Hi Ray:

Without knowing what's running on the machine, all those statistics
are just so many numbers.

Here's what matters: What applications are running and how much
resources are they using?

There's no mystery behind slow performance on a machine without
hardware problems. It's simply an imbalance of running applications
vs. resources available to run them (principally memory). The
solution is equally simple: Add resources or remove applications
that use too much of them.

Earl Grey

Ray Manning wrote:
I'm running an XP SP2 machine that has experienced an incredible
decrease in performance over the past couple months and I'm trying
to determine why. At first I thought the hard drive might be at
fault since I was seening It would appear to me that the machine
is
needlessly paging based on the PerfMon.exe Pages/sec counter and
the
taskman performance numbers. Can someone verify I'm on the right
track and possibly offer solutions?

Here's what I'm seeing:

Perfmon.exe (Pages/Sec) averages of 30-60 with a scale of 1

TaskMan: Performance

Physical Memory (K)

Total : 392,496
Available: 170,000
System Cache 240,000


Commit Charge(K)

Total 158,568
Limit 550,000
Peak 170,000

CPU usage averages about 5-20% but of course spikes at times.


What I don't understand, and perhaps it's my interpretation of the
perfmon counter, is why I have such a high page/sec rate when my
peak commit charge isn't even half of the physical memory.
Shouldn't my commit charge be much higher before paging starts
hitting 40+ pages/sec? Is page size 4k? 160k/second when I have a
couple hundred megs of physical memory available?

I did not look at these numbers before I started having
performance
problems (long boot times, 5 minutes to log on, etc) so perhaps
these are not out of line, but if not, can someone explain to me
what I'm missing in my interpretation?

Thanks,
Ray

.

Relevant Pages

  • Re: Excessive Paging
    ... Thanks Earl, I understand that. ... is normal with 392M memory, 160M of available memory and a max ... commit charge isn't even half of the physical memory. ... problems (long boot times, 5 minutes to log on, etc) so perhaps these ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: Excessive Paging
    ... is normal with 392M memory, 160M of available memory and a max ... device driver installed, the device enabled and yet the driver ... peak commit charge isn't even half of the physical memory. ... problems (long boot times, 5 minutes to log on, etc) so perhaps ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: Excessive Paging
    ... available memory and a max commit charge of 170M?" ... is normal with 392M memory, 160M of available memory and a max ... Earl Grey wrote: ... problems (long boot times, 5 minutes to log on, etc) so perhaps these ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: "normal" Boot times SBS 2003 SP1 Prem?
    ... > memory, drives, etc.)all impact this. ... > mins to around 10 mins... ... > typical boot times for SBS 2003 Prem SP1? ...
    (microsoft.public.windows.server.sbs)
  • [PATCH] Integrating SEP Driver with RAR Driver
    ... RAR stands for Restricted Access Region; this is memory ... This is upstream revision 4 of the SEP driver. ... +This functions maps and allocates the shared area on the external ...
    (Linux-Kernel)
Loading