Geek Answers Handbook

Eliminate UnionFS impact on test results inside Docker

I am trying to evaluate the overall system performance when starting Docker using Phoronix Test Suite 6.4.0 Milestone 2 running inside a container with fedora: 23 platform.

Keep in mind that Docker uses the patented UnionFS to store data. However, when you run a real application (for example, Apache) inside Docker, persistent data is usually stored in a dedicated folder on a host running on a standard Linux file system, such as ext4, or in my case btrfs.

The proposed solution is to use the docker level to mount the host directory in the docker. The fact is, I don’t know which directories should be used in the tests and should be installed inside the Docker container.

In the pts / disk test suite, you should definitely use dockers, not UnionFS. It contains these tests.

pts/compress-gzip pts/sqlite pts/apache pts/pgbench pts/compilebench pts/iozone pts/dbench pts/fs-mark pts/fio pts/tiobench pts/postmark pts/aio-stress pts/unpack-linux

What directories in the Docker container should be installed from the host (docker volumes made)? Is it even a good idea to use docker volumes? Are there any other caveats to consider when testing Docker?

+6
source share
1 answer

As mentioned in " Set Total Storage as Data Volume "

In addition to setting the host directory in your container, some Docker toner plugins allow you to provide and mount shared storage, such as iSCSI, NFS, or FC.

Starting with docker 1.9, this is done using docker volume create (and then you mount these volumes into the expected paths in the container)

This allows you to:

What directories in the Docker container should be installed from the host

Any folder that contains persistent data and / or has a large amount of I / O.

0
source

More articles:


All Articles