| commit | 4f83faa55af2d20185d615edf1806cba4b755832 | [log] [tgz] |
|---|---|---|
| author | Peter Johnston <peterjohnston@fuchsia.infra.roller.google.com> | Mon May 22 18:35:05 2023 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon May 22 11:36:33 2023 -0700 |
| tree | 2c71667d5e6d2bd36807dd5197a13cce638f3639 | |
| parent | d830ea567e4ec3f1d70b0c86da9de9ac9d3e288a [diff] |
[roll] Roll fuchsia [netstack/bench] Add resource usage benchmarks
Add a set of benchmarks that measure the netstack's memory consumption
and usage of kernel objects. The benchmarks take baseline measurements
after the netstack has started up, periodic measurements throughout to
measure peak resource usage, and final measurements afterward to
determine the amount of total increase in memory + handles held by the
netstack process.
During the benchmarks, run one of a set of workloads against the
netstack meant to exercise a particular subsystem. For example:
- Open many pairs of TCP or UDP sockets over loopback, send data, and
close the sockets.
- Install network interfaces, toggle them up/down, and send traffic
through them simulating neighbor solicitations.
Original-Bug: 118917
Test: fx test resource-usage-benchmarks
fx test --e2e netstack_benchmarks_test
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/835696
Original-Revision: 8d10c99da85ffeac29534340bdfa4abfb31ef3d2
GitOrigin-RevId: fd60974883b75ddfccf53d5926f26db19af98756
Change-Id: Ia47f0ec4452bda67bf730650c1dec6a49f784c07
This repository contains Fuchsia's Global Integration manifest files.
All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.
Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.