cAdvisor using 70% cpu about cadvisor HOT 8 CLOSED

This may be related to the leak in #26 since we leaked both a thread and memory. I will get a new release of the google/cadvisor image and let you know to try that.

Tomorrow, if we restart the container and the usage is low, I think it verifies that it is #26.

We do a bit of work per second housekeeping the containers, but a lot of that is a sleep in libcontainer which we're working on removing. In the end, we really only should need a few ms of CPU time per container for housekeeping. The most expensive part may be talking to Docker.

from cadvisor.

@erikh restarted cAdvisor and the usage went down to expected levels. This points to it likely being a dup of #26. Will build a new cAdvisor and provide it for verification.

from cadvisor.

thanks!

from cadvisor.

Pushed google/cadvisor:0.1.0 with the fixes. Let me know if that helps.

Also, any ideas how to re-tag latest? Do I just commit an image from a container made with google/cadvisor:0.1.0 and push that?

from cadvisor.

i think you have to tag latest by hand, so you tag an image with the version you want and then tag that same image with :latest

from cadvisor.

Ya, just tag the same image id with google/cadvisor:latest and push that

from cadvisor.

Looks like this was resolved with the latest image. Thanks guys!

from cadvisor.

Thanks for the report @erikh! I'll tag the new image latest (thanks @jchauncey and @crosbymichael!)

from cadvisor.