How to minimize hard faults to improve application performance?


we using window 2008 enterprise sp1 , run ibm websphere application server (was) 7 on it.

we monitored system resources , observed java processes lot of hard faults (page swapping) frequently, though there free memory available (about 65% used physical memory) total 16gb ram. 

i included inline image showing hard faults (red boxed).  cpu utilization not high there 400+ hard faults in each server. 




grateful can advise how can minimize hard faults in order optimize performance?

here response from larry miller, shed light on this:

dh correct, task manager shows both soft , hard page faults. in cases majority soft page faults not touch disk. microsoft article referenced wrong.

in case of hard page faults, majority not involve pagefile. task manager , performance monitor not tell ones do. paging occurs wide variety of files, not pagefile. in fact, disk io operations done paging. launching application , loading text file editor done paging.

disabling pagefile not reduce these other forms of paging. modified data written pagefile. when executable file or dll unloaded not written pagefile can reloaded original file. no pagefile modified data must remain in ram, if has not been accessed long time, if never accessed again. can put heavy strain on ram resources of system.

do not misled high "available" memory shown in task manager. majority of not free. in virtual memory system, memory being both available , in use not contradiction.

accurate source of information regarding windows internals publication "inside microsoft windows". heavy reading. articles intended general audience oversimplify things , make outright mistakes.



Windows Server  >  Windows Server General Forum



Comments

Popular posts from this blog

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

Failed to delete the test record dcdiag-test-record in zone test.com

Azure MFA with Azure AD and RDS