Hi,
I am running Unbound as a recursive resolver. I monitor the cache hit
ratio by dividing hits / total queries and I get a constant 41% while
there is a varying activity on the server.
I would expect the cache hit ratio vary in time and be more in the 80% mark.
I am looking for help for suggestions on how to improve the cache hit ratio.
Cache Hit Ratio Chart: http://dc1.soltysiak.com/chart2.php
Cache Contents Chart: http://dc1.soltysiak.com/chart.php
Does anybody have any ideas?
Cheers,
Maciej
Hello list!
Does anybody have any ideas about my constant cache hit ratio?
If it is of any help, here's my server section of unbound.conf for
inspection if anybody finds anything obvious.
It's a 512MB VM with 1 core.
server:
do-not-query-localhost: no
verbosity: 1
do-ip6: yes
prefetch: yes
msg-cache-size: 24m
rrset-cache-size: 24m
key-cache-size: 24m
infra-cache-numhosts: 40000
num-threads: 1
msg-cache-slabs: 1
rrset-cache-slabs: 1
infra-cache-slabs: 1
key-cache-slabs: 1
interface: 10.8.0.1
interface: ::1
interface: 127.0.0.1
# statistics-interval: 0
extended-statistics: yes
statistics-cumulative: no
access-control: 10.8.0.0/24 allow
access-control: 127.0.0.1 allow
access-control: A.B.C.D allow
access-control: ::1 allow
# The following line will configure unbound to perform cryptographic
# DNSSEC validation using the root trust anchor.
auto-trust-anchor-file: "/var/lib/unbound/root.key"
Best regards,
Maciej Soltysiak