Page Faults ???

[PinHead]

Would 5.8 million page faults in 18 hours be considered normal for this new client?

I thought the last client was high, but I was mistaken.

[IronBits]

I have 10 million in 13 hours - you're ok ;)

[pfb]

6.6 million in 14 hours here :)

[FoBoT]

i have a box with

431 million in 10 hours

is that bad?

what does it mean?

i am running "useram=0"

[FoBoT]

ok, i checked my longest running box

12 hours

1238 million

that is 1.238 BILLION page faults


is that bad?

this box is also running without the extra memory switch

do i win a cookie?

also, i have been using "progress=1" since the phase II client, there was that problem early on where it wasn't updating the something or other thingy, dfGUI jeff said to lower the progress to fix it

[Louis]

1.58 billion in 18 hours. I'M THE WINNER!

Well, so far. I want a cookie too - chocolate choc chip, or something similar.

BTW, this is on my work computer - 1Ghz P3, 128 MB, useram=0. I'm all the way to gen 42 on this protein - Got up to 180 or so before the switch. Yes, that's right, 180 generations, first set, on the first phase II protein. Average time per generation about 10 hours - I could the protein myself that fast!

(Hey Howard, just kidding.)

[PinHead]

Well here's M$'s definition:


The interrupt that occurs when software attempts to read from or write to a virtual memory location that is marked "not present."

In Task Manager, page fault is the number of times data has to be retrieved from disk for a process because it was not found in memory. The page fault value accumulates from the time the process started.


So if you are using the -rt switch, I don't understand why all the page faults.