Hi,
Please see: https://bugzilla.redhat.com/show_bug.cgi?id=1109651
ExecSum: if you flush the entire cache on network-connect, when
you have pre-fetching enabled, the entire cache is attempted to
be pre-fetched.
It would be good if user flushed records are not marked
for pre-fetch.
Paul
Hi Paul,
Hi,
Please see: https://bugzilla.redhat.com/show_bug.cgi?id=1109651
ExecSum: if you flush the entire cache on network-connect, when you
have pre-fetching enabled, the entire cache is attempted to be
pre-fetched.It would be good if user flushed records are not marked for
pre-fetch.
Unbound does not pre-fetch expired records. They are fetched
normally, i.e. when a user asks for it. So the cache flush does not
cause lookups. It also does not cause pre-fetch.
When a record is 'near expiry' then a pre-fetch happens (if prefetch
is enabled). This pre-fetch only happens when a user queries for that
record. The pre-fetch does not happen if the user does not query for
the record.
For that 400 queries part of the report. So unbound will only
generate an outbound query (except for trust-anchor updates on
schedule) when there is an inbound user query. Also for pre-fetch.
So, those 400 queries would only happen if the user is performing 400
lookups.
I am trying to deduce what unbound would do in theory. If in practice
this is not happening, some bug hunting is required. Does the user
have real data or are these his estimates? Perhaps his mobile
performs a lot of lookups when it connects to a hotspot, which is
possible, with, I don't know, a lot of apps.
Best regards,
Wouter