Re: 7.3.3 NT 4.0 Page faults = bad??

    Page faulting is a mechanism for sharing memory resources. Your virtual memory alocation is larger than actual amount of physical memory you/your job/your context have at any one time. hard faults mean your codes is in the page file otherwise its in physical memory. Faults are not a bad thing

                    Joe

Piotr Kolodziej wrote:

> Silent Bob wrote in message <36cd61b9.70451814_at_news.dial.pipex.com>...
> >On one of our servers oracle73.exe is generating about 900,000 page
> >faults a day. It uses not more than about 60 meg of the 256 meg page
> >file (and 128 mg ram)
> >Does anyone know what might be causeing these page faults (or even
> >what the page faults reading in NT task manager./processes really
> >means) And if this is bad or not...
> >There appears to be no performance problem.. but generating that many
> >page faults a day (something that I just noticed yesterday (oops) ) is
> >a little worrying. :-)
>
> AFAIK NT, instead of LRU, uses FIFO algorithm to manage pages
> in phisical memory. So you may see so large number of page faults.
> But in most cases, these are "soft" page faults and faulting page
> is found in the file cache.
> If you're worry about paging activity you should
> see page inputs / outs statistics. It reflects disk activity.
> In general, you should avoid more than 5-10 "hard" page swaps
> per second in whole system.
>
> --
> Piotr Kolodziej pkol_at_otago.gda.pl
> Just my private opinion.
Received on Fri Feb 19 1999 - 14:12:34 CST