Fewer Optimistic Cache Hits On v0.107.70

[7gxycn08]

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)

Windows, AMD64 (aka x86_64)

Installation

GitHub releases

Setup

On one machine

AdGuard Home version

AdGuard Home v0.107.70

Action

With the new update average dns processing time increased tremendously it rarely uses cache now with the new update.

Average processing time increased from 0ms to 400ms.

Expected result

Previously it always used the cache and refreshed in the background when it became stale as described In the settings tool tip message.

Average processing time was under 1ms when cache is properly filled.

Actual result

It's rarely using cache now.

Additional information and/or screenshots

Before the update avg processing time was less than 1ms now it's 400ms and cache is rarely used.

[goppinath]

I can confirm this issue. It appears that optimistic caching is not working at all. I no longer see any stale answers with a TTL of 10, which I consistently saw before update v0.107.70.

This might be a side effect of introducing:

• dns.cache_optimistic_answer_ttl
• dns.cache_optimistic_max_age

As a result, my AdGuard Premium DNS is now receiving slightly more requests. The increase is small, likely because stale answers in earlier versions already triggered background cache refreshes.

My schema version is still 31, and I’m running v0.107.70.

I’ve attached a screenshot of my current settings.

[Septrum101]

It seems happened in using ipv6 addr. I cannot see any cache from the log.

[TNOTA]

I can also confirm this. Cache appears to not be used much at all anymore. Almost all queries going to upstream server to be resolved.

[EugeneOne1]

Hello @7gxycn08, and thanks for the report. We've found the bug and fixed it in the latest beta and edge releases. We're currently preparing a hotfix.

[TheCeet]

• @EugeneOne1 when release in production?
  Today or next week?

[EugeneOne1]

@TheCeet, we're going to release it as soon as possible – probably on 8 December, the date assigned to the milestone.

[yuxuan0107]

我当前也发现了这个问题，另外我还想咨询一下107.7这个版本中新增加的两个参数应该如何配置，它的作用是什么I have also found this problem at present, and I would also like to ask how to configure the two newly added parameters in 107.7 and what their functions are.

[vjl]

@7gxycn08 Unrelated to this bug, but what did you use to get the screenshot you included with your bug report? Thank you!