From 5b3f25047fe8dd4d04262ea56c38a134291d0067 Mon Sep 17 00:00:00 2001 From: Zach Koopmans Date: Mon, 13 May 2019 15:03:34 -0700 Subject: Upload latest set of benchmarks Also includes redis density benchmark. --- content/docs/architecture_guide/performance.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'content') diff --git a/content/docs/architecture_guide/performance.md b/content/docs/architecture_guide/performance.md index b6286cf95..f31baa5e1 100644 --- a/content/docs/architecture_guide/performance.md +++ b/content/docs/architecture_guide/performance.md @@ -85,7 +85,7 @@ For many use cases, fixed memory overheads are a primary concern. This may be because sandboxed containers handle a low volume of requests, and it is therefore important to achieve high densities for efficiency. -{{< graph id="density" url="/performance/density.csv" title="perf.py density --runtime=runc --runtime=runsc" >}} +{{< 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) @@ -134,7 +134,7 @@ supports a variety of platforms. These platforms present distinct performance, compatibility and security trade-offs. For example, the KVM platform has low overhead system call interception but runs poorly with nested virtualization. -{{< graph id="syscall" url="/performance/syscall.csv" title="perf.py syscall --runtime=runc --runtime=runsc-ptrace --runtime=runsc-kvm" log="true" >}} +{{< graph id="syscall" url="/performance/syscall.csv" title="perf.py syscall --runtime=runc --runtime=runsc-ptrace --runtime=runsc-kvm" y_min="100" log="true" >}} The above figure demonstrates the time required for a raw system call on various platforms. The test is implemented by a custom binary which performs a large -- cgit v1.2.3