bench: add --vs-adguard mode for Numa vs AdGuard Home comparison

AdGuard Home on port 5457, both forwarding via DoH. Cached queries
tied at 0.1ms. On degraded networks hedging hurts p99 (28ms vs 10ms
without) — both requests pay the same high RTT with no random spikes
to rescue. On clean networks hedging wins.
This commit is contained in:
Razvan Dimescu
2026-04-13 00:56:58 +03:00
parent 274338e7f9
commit 501902d569

View File

@@ -8,6 +8,7 @@
//! --hedge-5x Hedging: single vs hedge-same vs hedge-dual vs Hickory (5 iterations)
//! --vs-unbound Server-to-server: Numa vs Unbound (plain UDP, caching)
//! --vs-unbound-cold Cold: Numa vs Unbound (unique subdomains, no cache hits)
//! --vs-adguard Server-to-server: Numa vs AdGuard Home (plain UDP, caching)
//! --vs-nextdns Server-to-cloud: Numa (local cache) vs NextDNS (remote, 45.90.28.0)
//! --vs-dot DoT server: Numa vs Unbound
//! --vs-doh-servers DoH server: Numa vs Unbound (DoT upstream)
@@ -158,6 +159,10 @@ fn main() {
check_numa_mode(&rt, "forward");
return run_server_comparison(&rt, "dnscrypt-proxy", "127.0.0.1:5455", 5, false);
}
if arg("--vs-adguard") {
check_numa_mode(&rt, "forward");
return run_server_comparison(&rt, "AdGuard Home", "127.0.0.1:5457", 5, false);
}
if arg("--vs-nextdns") {
check_numa_mode(&rt, "forward");
return run_server_comparison(&rt, "NextDNS", "45.90.28.0:53", 5, false);