Should the pagefile be used even if I have sufficient physical memory?


or perhaps better question:

is there reliable application-agnostic method of determining when detrimental memory paging occuring?

so far using perfmon counter "% usage" under "paging file" performance object.  notice % usage high, though memory:"commited bytes" under physical ram amount.

memory:"page reads/sec" appear healthy.  i'll see spike when application opened settle down zero.

this not single fluke case, notice on variety of our servers.  wondering if normal or if memory upgrades in order.

thanks,
jaime

the pagefile used when free ram available design.

processes less activity paged away make room other memory claims. consider windows first using ram. in case ram full , new application started, windows should identify processes can paged away, read them ram, write them disk, read teh new program disk , load in freed ram. consumes lot of time disk read/write slow operation, , while user waiting program start.

so work around performance hit, windows monitor memory usage , page away not used keep ram free new processes might start.

 


mcp/mcsa/mcts/mcitp


Windows Server  >  Windows Server General Forum



Comments

Popular posts from this blog

2008 Windows Deployment Server Properties Error

Can no longer user MS Update - Files required to use Microsoft Update are no longer registered

How do a find data in one file, search for it in another file and if not found, write a custom message to another file