(imported topic written by mmurty)
I am seeing a high amount page faults on client server and high memory usage. Is there any specific reason and how can this be resolved? I see this in the Task Manager. Any suggestions would be appreciated.
(imported comment written by BenKus)
Hi mmurty,
You will need to define “high”. The BES Agent will tend to use 2-7 MB of memory and since the BES Agent is a “continuous evaluation” agent, it will be slowly looking at files, registry keys, configurations, etc. When the agent looks at a file or registry or anywhere else, it is constrained to use less than 1-2% of the overall system’s resources (including CPU and disk IO). The page faults are cumulative so if you leave a computer on for a long time, it will look like there are lots of page faults, but they are very slowly accumulating as the client slowly checks the computer and the page faults won’t affect the overall performance of the system.
More info at:
http://support.bigfix.com/cgi-bin/kbdirect.pl?id=43
Ben
(imported comment written by claydean91)
But what actually causes the page faults? On a SQL server here within task manager the BesClient is showing a hell of a lot of them??
(imported comment written by BenKus)
A “page fault” means that the agent requested data that was not in memory. This is to be expected because the agent is slowly checking files/reg keys/other parts of the system in the background… The counters in Task Manager show the cumulative page faults and since our agent runs for as long as the computer is running, it looks like a lot, but since it is checking so slowly (1-2% of the system resources) then it doesn’t affect performance.
Also, some of the page faults as reported by Task Manager don’t actually mean the computer needs to get the data from disk because there are other cache elements that kick in and so we are commonly blamed for page faults that make it appear like lots of disk activity even though the disk doesn’t need to service our request.
Ben