It runs from the host, so you don’t need to do anything other than have Docker installed.Īnother helpful tool is the /sys/fs/cgroups directory. ![]() It displays each container and its CPU usage, memory usage, and other resource information. ![]() One helpful Docker-specific tool is docker stats, which is a top-like tool for monitoring the status of running Docker containers. In my case, running pidstat and mpstat was sufficient to discover the cause of my slow builds. I recommend that you install these inside of your Docker containers to help with performance analysis. Netflix has an excellent post called Linux Performance Analysis in 60,000 Milliseconds which recommends some good tools. Basic observabilityīefore diving too deeply into perf or eBPF to look for performance problems, it helps to know where to start. ![]() You can also just use -pid=host if you want to start any other Docker container to inspect running processes. This gives you full access to the Docker VM. $ docker run -it -rm -privileged -pid =host justincormack/nsenter1
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |