Hello All
I got one customer reporting very high I/O in windows 2008 server, he’s showing a graphic with BES Client in that server using peaks of 8 to 10 kilobytes per second. How much is much regarding I/O for a BES Client, do you have any experience talking about this counts?
There’s content (analysis and fixlet) in the “BES Support” site to manage CPU utilization of the BESClient on managed endpoints. Under the fixlet & tasks section of that site you can search for “CPU”. There are 5 options with that fixlet, and #2 is the default.
That said, by default the BESClient will utilize between 1-2% of available CPU and roughly 10MB of RAM. These obviously changes when actions are issues to an endpoint.
Have you checked to see what actions have been issued to the endpoint in question? If the issues persist, it may be necessary to enable BESClient debug logging and then open an PMR with the daily and debug logs.
1 Like
Also note that the 1-2% is per CPU; so be sure to multiply it by the number you have on your endpoint and adjust accordingly.
1 Like
Are you able to share the graphic/screenshot, or provide more details on the specific metric being measured? Note that in some contexts, IO on Windows is not limited to disk, but also includes network.
1 Like
Also, they will want to ensure that any AV is configured to not scan the BES Client folder “On Access”.
2 Likes
Hello @cmcannady
Sorry for the late reply.
In fact, currently the only Analyses that are running are the ones of BFI. The actions also those of BFI.
HI @TimRice
Yes, exclusion of BF folders was the first thing I recommend to the customer, after 1 weeks he finally did it, but still its complaining…
Hi @Aram
(Sorry for the late reply to all.)
This is the best graphic the customer had share:
-In the left is the behavior of the server (agent) when the customer report the issue (high IO)
-In the center: the customer stopped the agent
-Center-Right the customer start again the agent
-At the right is when I adjusted the CPU Usage to be “very low CPU usage (< .5%)”
I guess the KB/second part is not very legible, at the bottom is 0 and at the top of the picture is 12 K/sec
The customer still consider the IO that comes from BES Client is HIGH.
What you guys think?
That is pretty high write I/O. I’d double check the client log to make sure that nothing is running on the client.
The client generally only does what you tell it to – double check the client log and maybe enable debug logging to see what the client is working on.
2 Likes
Definitely, you need to double check if there are actions that are running and what they do.
1 Like
Should also check to see what logging levels are active. If BESClient debug logging in enabled, it can generate quite a bit of data.
1 Like