Update to Adguard under HA caused increased processing time

[hokfujow]

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

Custom package (OpenWrt, HomeAssistant, etc; please mention in the description)

Setup

On one machine

AdGuard Home version

5.0.5

Action

Updated HA adguard addon

Expected result

No change in adguard performance

Actual result

10X increase in processing time reported on adguard dashboard.

Additional information and/or screenshots

Running HA on a R Pi 4000 with adguard addon. Has been working very well for quite some time. Previously saw processing times around 5ms. Today an update was offered which I installed (5.0.4 to 5.0.5) After installing the update, processing time reported on the dashboard went from around 5ms to over 80ms. I restored the previous version from HA backups and processing time dropped back down to previous value.
Note I also run Adguard standalone on a different R Pi. Installing the update there (which shows as version
v0.107.46) did not cause the same issue.

[Cebeerre]

Could you please elaborate this a bit more ? Which upstream servers are you using ? What's the current average response time per upstream ?

[hokfujow]

Hi - just to clarify - it wasn't the upstream response time that changed. It was the Adguard processing time shown separately in the interface (top left pane). Average upstream responses range from 11ms to about 80ms. As I said, when i downgraded back to the previous version, the response time went back to less than 5ms. Usually between 1 and 3ms. Michael ᐧ

…

On Mon, Mar 25, 2024 at 4:37 AM Xavi ***@***.***> wrote: Could you please elaborate this a bit more ? Which upstream server are you using ? What's the current average response time per upstream ? — Reply to this email directly, view it on GitHub <#6850 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABUXSVYQA4JMXXP3RTP4V3YZ7O4JAVCNFSM6AAAAABFF44M2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJXGQ3TCNBQGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[ghost]

To determine whether the issue is with the original package or the HA package, do you experience this with the non-HA version also?

[hokfujow]

Both. I believe I tracked this down t the setting for private reverse DNS lookup. When i set this explicitly to my router address, the problem went away. Previously it was left blank to use the default values. I wonder if something changed in a recent AGH release that related to how it handled leaving this field empty with reverse lookup enabled, because: 1) Now, leaving it blank causes long processing times, but entering router address restores previous short time 2) In previous releases, leaving that field blank did not lead to long processing time.

…

On Sun, Apr 21, 2024 at 3:33 PM jslawler-gh ***@***.***> wrote: To determine whether the issue is with the original package or the HA package, do you experience this with the non-HA version also? — Reply to this email directly, view it on GitHub <#6850 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABUXSRI2P4XSLRP7DRE63DY6QIBLAVCNFSM6AAAAABFF44M2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRYGE3TIOJXHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>