go
/
gvisor
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixup redis container count.

This commit is contained in:
Adin Scannell 2019-05-13 15:20:45 -07:00 committed by Adin Scannell
parent 9ea68ce165
commit ad7ef8410f
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
content/docs/architecture_guide/performance.md
View File

@ -88,12 +88,12 @@ therefore important to achieve high densities for efficiency.
{{< graph id="density" url="/performance/density.csv" title="perf.py density --runtime=runc --runtime=runsc" log="true" y_min="100000" >}}
The above figure demonstrates these costs based on three sample applications.
This test is the result of running many instances of a container (typically 50)
and calculating available memory on the host before and afterwards, and dividing
the difference by the number of containers. This technique is used for measuring
memory usage over the `usage_in_bytes` value of the container cgroup because we
found that some container runtimes, other than `runc` and `runsc`, do not use an
individual container cgroup.
This test is the result of running many instances of a container (50, or 5 in
the case of redis) and calculating available memory on the host before and
afterwards, and dividing the difference by the number of containers. This
technique is used for measuring memory usage over the `usage_in_bytes` value of
the container cgroup because we found that some container runtimes, other than
`runc` and `runsc`, do not use an individual container cgroup.
The first application is an instance of `sleep`: a trivial application that does
nothing. The second application is a synthetic `node` application which imports