Thank you kevan for the info!
So might I suggest a post rpm script in the s390x rpm that says warns the
customer that default settings should be examined for a z/VM environment. If
we had that info as we piloted the rpm install on the few "lab" servers we
have, we might have been able to stop
We had the documentation updated to take into account highly virtualised
environments:
https://www.ibm.com/support/knowledgecenter/en/SS6MER_9.5.0/com.ibm.bigfix.doc/Platform/Config/c_virtual_machines.html
You can also set time periods where the agent doesn't run at all, e.g.
prime shift. If you
Last call for registrations for Thursday’s Hillgang meeting in Herndon
Virginia. Logistics and abstracts: http://www.vm.ibm.com/events/HILL0318.PDF
Registration at: https://doodle.com/poll/fvg86gk7hdkwk6f2
Neale
--
For LINUX-39
Hi
I had a similar problem with it (not sure if it is the same problem).
By default the client consumes 2 or 5% cpu... it uses some kind of polling
mechanism.
When you have many guests this builds up...
We configured it to consume 0.2% cpu or something like that...
That only affected how fast the
When it was first installed on my zLinux servers, BESCLIENT used 2-5% of the
CPU available to each guest. We didn't have the extra CPU for this increase on
26 guests. I contacted the team that implemented it and they were able to
tweak a parameter that reduced the CPU overhead to less than 1%.
Oh yea. Been there...
It uses 2% of an IFL by default. Not so great when you have many many servers
This is from IBM on how to tame it.Basically you need to tell it you are a
laptop that needs to go to sleep :)
The settings go on the bigfix master, not the client end.
--
A couple of days ago our VM's begin a sustained increase in CPU usage. We began
an investigation checking recently changes on the LPAR's and the guests. The
only thing we found is that inside all the guests the BESCLIENT was installed.
Although it the process doesn't show high CPU utilization, w
