Repository navigation
Conversation
ygao-g
force-pushed
the
nighthawk-egress-b1-lib
branch
2 times, most recently
from
November 6, 2026 17:51
188b5d1 to
8647a6d
Compare
ygao-g
changed the base branch from
nighthawk-egress-base
to
nighthawk-ingress-rates
November 6, 2026 17:51
ygao-g
force-pushed
the
nighthawk-ingress-rates
branch
from
November 6, 2026 18:15
ff812be to
c51ca95
Compare
ygao-g
force-pushed
the
nighthawk-egress-b1-lib
branch
from
November 6, 2026 18:15
8647a6d to
ae29932
Compare
ygao-g
force-pushed
the
nighthawk-ingress-rates
branch
from
November 6, 2026 18:53
c51ca95 to
3f71a82
Compare
ygao-g
force-pushed
the
nighthawk-egress-b1-lib
branch
from
November 6, 2026 18:53
ae29932 to
11ec01c
Compare
ygao-g
force-pushed
the
nighthawk-ingress-rates
branch
from
November 6, 2026 19:09
3f71a82 to
24847c9
Compare
ygao-g
force-pushed
the
nighthawk-egress-b1-lib
branch
2 times, most recently
from
November 6, 2026 21:53
28cfbc4 to
ba3e550
Compare
Rename _builtin_key, _global_result and _counters to builtin_key, global_result and counters, because nighthawk-egress/output.py imports them in the next commit. capacity_summary() takes actors as an optional argument and emits it only when given, since the egress benchmark has no actor fleet. build_session_spec() treats a tail_latency_slo_ms of 0 as disabled, as the ingress README documents. Signed-off-by: Yuan Gao <ypgao@google.com>
ygao-g
force-pushed
the
nighthawk-ingress-rates
branch
from
November 9, 2026 23:26
24847c9 to
af0a3db
Compare
ygao-g
force-pushed
the
nighthawk-egress-b1-lib
branch
from
November 9, 2026 23:26
ba3e550 to
602805c
Compare
…nter parser Define the egress-specific failure predicates and Nighthawk template for the adaptive load search, targeting the atenet-egress gateways. Add the prometheus output parser for the egress metrics. Signed-off-by: Yuan Gao <ypgao@google.com>
benchmarking/nighthawk-egress/tests covers spec.py and output.py. Add the suite to benchmarking-python.sh so it runs with the other benchmarking suites. Signed-off-by: Yuan Gao <ypgao@google.com>
ygao-g
force-pushed
the
nighthawk-egress-b1-lib
branch
from
November 11, 2026 22:42
602805c to
2f1e219
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The egress gateway has a manual Nighthawk setup, but no benchmark that searches for its capacity. Such a benchmark needs a load definition for each egress mode:
http,mitmandpassthrough. It also needs proof that the load went through the gateway path of that mode. A rate that is measured on another path is not a capacity of the mode.A new library, with tests, provides both parts. The first part builds the adaptive Nighthawk session for each mode, with the TLS settings of that mode. The second part reads the gateway counters from before and after a run, and adds the differences and four checks to the capacity summary. The checks are
ext_proc_invariant_ok,mode_exclusivity_ok,forward_proxy_overflow_okandgateway_counter_reset. Nothing calls the library until the runner is added. In the shared Nighthawk library, atail_latency_slo_msof 0 now disables the latency threshold, as the nighthawk-ingress README states.Part of agent-substrate#3624
AI use: AI-assisted for the diff, the split and the test runs; I reviewed the diff.