This directory contains a number of tests to help measure container
memory footprint. Some measures are based around the
PSS of the runtime
components, and others look at the system level (free and /proc/meminfo
for instance) impact.
This test measures the PSS footprint of the runtime components whilst launching a number of small (BusyBox) containers using ctr.
This test takes system level resource measurements after launching a number of containers in parallel and optionally waiting for KSM to settle its memory compaction cycles.
The script is quite configurable via environment variables, including:
- Which container workload to run.
- How many containers to launch.
- How many containers are launched in parallel.
- How long to wait until taking the measures.
See the script itself for more details.
This test shares many config options with the footprint_data test. Thus, referring
to the footprint test documentation may be useful.
Note: If this test finds KSM is enabled on the host, it will wait for KSM to "settle" before taking the final measurement. If your KSM is not configured to process all the allocated VM memory fast enough, the test will hit a timeout and proceed to take the final measurement anyway.
Similar to the fast_footprint test, but this test launches the containers
sequentially and takes a system level measurement between each launch. Thus,
this test provides finer grained information on system scaling, but takes
significantly longer to run than the fast_footprint test. If you are only
interested in the final figure or the average impact, you may be better running
the fast_footprint test.
For more details see the footprint test documentation.
Measures the memory statistics inside the container. This allows evaluation of the overhead the VM kernel and rootfs are having on the memory that was requested by the container co-ordination system, and thus supplied to the VM.