Yuksel Thank you for that information and I'm sorry I haven't responded sooner (other work took precedence, as is so often the case).
Your modification to the 'run' command has worked exactly as required. I now have cadvisor running on my zcx system and overall CPU utilisation is down to a much more reasonable 5-6% - a very welcome change! Thanks you again Regards Sean On Wed, 2 Sep 2020 at 22:09, Yuksel Gunal <ygu...@linux.vnet.ibm.com> wrote: > Hi Sean, > > cAdvisor polls for metrics once a second by default. Though I have not > seen such high CPU utilization with the default setting, it is worth to run > cAdvisor with a different setting, one that you can define explicitly when > you start cAdvisor. I'd recommend that you try a 10s or 15s interval and > see if either helps. To do that, you need to specify the > "--housekeeping_interval" parameter. Here is how you'd do it on zCX (sets > it to 10 seconds): > > docker run -v /:/rootfs:ro -v /var/run:/var/run:ro -v /sys:/sys:ro -v > /var/lib/docker/:/var/lib/docker:ro -v /dev/disk/:/dev/disk:ro -p 8080:8080 > -d --network monitoring --name=cadvisor ibmcom/cadvisor-s390x:0.33.0 > cadvisor --housekeeping_interval=10s > > Note that I modified the instructions by adding "cadvisor > --housekeeping_interval=10s" > > Also, Prometheus polls cAdvisor, but cAdvisor's data collection is not > triggered by Prometheus polling. It has its own polling cycle and it keeps > the metrics in memory. When Prometheus polls cAdvisor, it returns the last > set of collected metrics from memory. > > Yuksel Gunal > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
