summaryrefslogtreecommitdiffhomepage
path: root/content/docs
diff options
context:
space:
mode:
authorzkoopmans <zkoopmans@google.com>2019-05-02 10:02:44 -0700
committerAdin Scannell <adin@scannell.ca>2019-05-13 15:27:34 -0700
commit07c8695865899ef7b60c92cb861e500dfc65c3ff (patch)
tree89cf56de0c317391d8773f33dc02d005cfc2f8dc /content/docs
parentb879aa444d0a2a87c892296ed5f7ec62842da6eb (diff)
Update fio to display in log scale
Diffstat (limited to 'content/docs')
-rw-r--r--content/docs/architecture_guide/performance.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/content/docs/architecture_guide/performance.md b/content/docs/architecture_guide/performance.md
index 58339dffb..ab0237ac2 100644
--- a/content/docs/architecture_guide/performance.md
+++ b/content/docs/architecture_guide/performance.md
@@ -205,13 +205,13 @@ through the [Gofer](../) as a result of our [security model](../security/), but
in most cases are dominated by **implementation costs**, due to an internal
[Virtual File System][vfs] (VFS) implementation the needs improvement.
-{{< graph id="fio-bw" url="/performance/fio.csv" title="perf.py fio --engine=sync --runtime=runc --runtime=runsc" >}}
+{{< graph id="fio-bw" url="/performance/fio.csv" title="perf.py fio --engine=sync --runtime=runc --runtime=runsc" log="true" >}}
The above figures demonstrate the results of `fio` for reads and writes to and
from the disk. In this case, the disk quickly becomes the bottleneck and
dominates other costs.
-{{< graph id="fio-tmpfs-bw" url="/performance/fio-tmpfs.csv" title="perf.py fio --engine=sync --runtime=runc --tmpfs=True --runtime=runsc" >}}
+{{< graph id="fio-tmpfs-bw" url="/performance/fio-tmpfs.csv" title="perf.py fio --engine=sync --runtime=runc --tmpfs=True --runtime=runsc" log="true" >}}
The above figure shows the raw I/O performance of using a `tmpfs` mount which is
sandbox-internal in the case of `runsc`. Generally these operations are