You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All of these items should compare Native Linux vs Cage times for this. Ideally, we could change the cage or Native stack when doing this so be explicit about the cage technology stack and native stack when providing data. For example, list versions of software and whether this is NaCl + RustPOSIX or Wasm + RawPOSIX, etc.
For each test, also do a reasonable breakdown of where the time cost comes from when possible. This need not be extensive and we can iterate on this later.
Benchmark List:
fork comparison
exec comparison
signal overhead
context/cage switch overhead
system call/microvisor call overhead
LAMP stack total memory use comparison
Python benchmark (computation only)
Macro benchmarks of real world application stacks. We should have a cadre of these which we can add to
Pipe benchmark
Unix Domain Socket benchmark
Loopback benchmark
/proc, /dev/urandom, etc. benchmark
The text was updated successfully, but these errors were encountered:
Issue to track our desired benchmarks for Caging.
All of these items should compare Native Linux vs Cage times for this. Ideally, we could change the cage or Native stack when doing this so be explicit about the cage technology stack and native stack when providing data. For example, list versions of software and whether this is NaCl + RustPOSIX or Wasm + RawPOSIX, etc.
For each test, also do a reasonable breakdown of where the time cost comes from when possible. This need not be extensive and we can iterate on this later.
Benchmark List:
The text was updated successfully, but these errors were encountered: