Upstream latency increase since v0.107.55

[RainmakerRaw]

Prerequisites

• I have checked the Wiki and Discussions and found no answer

• I have searched other issues and found no duplicates

• I want to report a bug and not ask a question or ask for help

• I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)

Platform (OS and CPU architecture)

Linux, ARM64

Installation

GitHub releases or script from README

Setup

On one machine

AdGuard Home version

0.107.55

Action

Replace the following command with the one you're calling or a
description of the failing action:

N/A

Expected result

Upstream latency should be in line with my ISP WAN connection (FTTP/fibre), approx 12ms.

Actual result

Since upgrading to 0.107.55 the upstream latency has drifted, a fair amount. I am aware that the release is intended to address latency issues (eg #6818), ironically.

On previous versions (eg 0.107.54) my upstream latency across 24 hours is approximately 12ms-14ms for most upstreams. After upgrading to 0.107.55 the upstreams are between 17ms and 32ms. I have verified this multiple times, on the same home LAN with the same clients and (roughly) the same type of traffic. I have tested on my primary LAN DNS server (bare metal, Radxa Rock5B, Debian Bookworm aarch64), and also confirmed the same issue on my backup instance (Alpine Linux LXC on Proxmox, AMD Ryzen x86_64 host).

Downgrading to 0.107.54 immediately fixes the issue, and upstream latency returns to around 12ms. I have pprof running, and can switch versions and/or collect stats and logs as required. Many thanks in advance.

Additional information and/or screenshots

Here is a redacted copy of the AdGuardHome.yaml (extension changed to .txt for Github).
AdGuardHome.txt

[tjharman]

Thank you for the report - I will pass it on to the devs.
Can you confirm if you're using caching or not please? I've tried parsing your uploaded config (thank you) but can't spot it myself.

[RainmakerRaw]

The DNS cache, you mean?

  cache_size: 10000000
  cache_ttl_min: 0
  cache_ttl_max: 0
  cache_optimistic: true

[EdinburghWG]

I have a similar issue but this isn't just related to the latest version. I believe it occured a couple of versions before. I have three addresses to which parallel requests are made:

tls://dns.google
tls://1dot1dot1dot1.cloudflare-dns.com:853
tls://one.one.one.one:853

Bootstrap DNS addresses are:

1.1.1.1
1.0.0.1
2606:4700:4700::1111
2606:4700:4700::1001

With the above, the average upstream response time is 22ms for Google and 23/24ms for Cloudflare. Removing the Google address automatically and immediately increases the response time to 32ms.

Also, the display of the average upstream response time should be from the quickest at the top to the least quick one at the bottom. Currently, it's the other way round suggesting that the least quick one is the quickest.

[pendie]

I am also here the same and back to v0.108.0-b.59 everything is running normally again it seems all version 5 causes latency increase version 49 is very good