Finally, when investigating page fault issues, it is important to understand whether the page faults are hard faults or soft faults. The page fault counters in Performance Monitor do not distinguish between hard and soft faults, so you have to do a little bit of work to determine the number of hard faults.
A page fault is a trap to the software raised by the hardware when a program accesses a page that is mapped in the virtual address space, but not loaded in physical memory. (emphasis mine) Okay, that makes sense. But if that's the case, why is it that whenever the process information in Process Hacker is refreshed, I see about 15 page faults?
Estava lendo a resposta do usuário Maniero a respeito de overlay e gerenciamento de memória. Ele citou o page fault que pode ocorrer quando um programa está sendo executado. Entretanto, este termo ...
The page fault handler needs to (1) allocate a physical page frame ; (2) load the data from secondary story into the page frame; (3) update the page table to indicate the logical page to physical page frame mapping; and (4) restart the instruction that caused the fault.
Page faults are divided into two types, soft and hard. A page fault occurs when a process requests a page in memory and the system cannot find the page at the requested location. If the requested page is actually elsewhere in memory, then the fault is a soft page fault. However, if the page has to be retrieved from the disk, then a hard fault ...
Increasing the physical RAM on your machine could result in fewer page faults, although design changes to your application will do much better than adding RAM. In general, having a smaller memory footprint, and having things that will often be accessed around the same time be on the same page will decrease the number of page faults.