Is this many cache misses with unbound normal?

[Arimil]

Code Select Expand

Total
Recursion time (average):    0.107628
Recursion time (median):    0.077739
TCP usage:    0
IP ratelimited queries:    0
Recursive replies:    13412
Cache misses:    13412
Cache hits:    1275
Serve expired:    0
Prefetch:    1200
Queries:    14687
Request queue avg:    0.238434
Request queue max:    23
Request queue overwritten:    0
Request queue exceeded:    0
Request queue size (all):    0
Request queue size (client):    0
Times
Now:    1739705201.337157
Uptime:    40561.484009
Elapsed:    40561.484009

This is after running for a few hours, the only settings I changed are:

Code Select Expand

Prefetch Support: ON
Message Cache Size: 20m
Number of Hosts to cache: 50000

Which I believe these changes to make cache hits more common, but this many misses seems fairly bad to me.

[Patrick M. Hausen]

You could enable the query log and then some scripting to find out if these are all unique requests.

You have not said anything about the environment or the number and type of clients. Also look at the recursion times - why do you think the time to resolve a lookup is even relevant? You have .07 seconds median. Users are not noticing that.

[Arimil]

You have not said anything about the environment or the number and type of clients

This is a homelab setup so not many clients:
- a few cellphones
- a few TV
- a desktop
- a NAS with various containers running on it

That's about it, you're correct I haven't noticed it be problematic, this is just my first time using unbound and this seemed out of the ordinary to me so I wanted to ask.

[Arimil]

I do believe I know what is happening now, I'm running adguard in front of this which is also caching requests, I'm assuming adguard is caching them long enough that they are falling out of the unbound cache which is why almost all of the requests are cache misses.