gvisor/test/benchmarks/network
Adin Scannell ffa9a715aa Simplify profiling and benchmarks.
- Tweak the benchmarks to work with b.N where appropriate. In many cases,
  b.N was simply being ignored. This creates an implicit dependency in the
  user passing a reasonable benchtime (less than or equal to the actual
  runtime of the test, or using the X syntax) otherwise the test runs
  forever.
- In cases where the above is impossible, explicitly set benchtime from
  the test wrapper, to prevent the above behavior (tensorflow).
- Drop the *Reverse variants, which are simply hey benchmarks. We should
  just add a hey benchmark. The platforms benchmarks already include a
  native platform, and thus these benchmarks are incredibly confusing.
  (In other words, BenchmarkNginxReverse has nothing to do with an nginx
  benchmark for runsc.)
- Remove the redunant Harness object, which contains no state, in order
  to slightly simplify the code.
- Make Block and Heap profiling actually work, but setting appropriate
  runtime parameters (and plumbing them through the config).
- Split the profiling into two phases: start and stop, since some will
  need to be started early, and others will need to happen at the end.

PiperOrigin-RevId: 349495377
2020-12-29 18:29:12 -08:00
..
BUILD
httpd_test.go Simplify profiling and benchmarks. 2020-12-29 18:29:12 -08:00
iperf_test.go Simplify profiling and benchmarks. 2020-12-29 18:29:12 -08:00
network.go Simplify profiling and benchmarks. 2020-12-29 18:29:12 -08:00
nginx_test.go Simplify profiling and benchmarks. 2020-12-29 18:29:12 -08:00
node_test.go Simplify profiling and benchmarks. 2020-12-29 18:29:12 -08:00
ruby_test.go Simplify profiling and benchmarks. 2020-12-29 18:29:12 -08:00