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

Fix grammar mistake in Performance Guide 

Fixes #147
This commit is contained in:
Ian Lewis 2020-03-12 18:14:31 -04:00 committed by Zach Koopmans
parent 95535eca24
commit 14c1917b70
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -25,9 +25,9 @@ Second, as gVisor is an independent implementation of the system call surface,
many of the subsystems or specific calls are not as optimized as more mature many of the subsystems or specific calls are not as optimized as more mature
implementations. A good example here is the network stack, which is continuing implementations. A good example here is the network stack, which is continuing
to evolve but does not support all the advanced recovery mechanisms offered by to evolve but does not support all the advanced recovery mechanisms offered by
other stacks and is less CPU efficient. This an **implementation cost** and is other stacks and is less CPU efficient. This is an **implementation cost** and
distinct from **structural costs**. Improvements here are ongoing and driven by is distinct from **structural costs**. Improvements here are ongoing and driven
the workloads that matter to gVisor users and contributors. by the workloads that matter to gVisor users and contributors.
This page provides a guide for understanding baseline performance, and calls out This page provides a guide for understanding baseline performance, and calls out
distint **structural costs** and **implementation costs**, highlighting where distint **structural costs** and **implementation costs**, highlighting where