>>> If yes, message cache elements are prefetched before they expire >>> to keep the cache up to date. Default is no. Turning it on >>> gives about 10 percent more traffic and load on the machine, but >>> popular items do not expire from the cache.
>My question earlier still stands: does Unbound do what HAMMER says >(waits for a request before refreshing the cache) or does it just >refresh the cache automatically? The Unbound doc is unclear (at least >to me). If it did it automatically, I'd expect a lot more than 10% more traffic. I enabled it on my not terribly busy server and I see numbers that look like they're in the 1% range: Jul 03 14:23:21 unbound[40669:0] info: server stats for thread 0: 47798 queries, 20108 answers from cache, 27690 recursions, 242 prefetch Jul 03 15:23:21 unbound[40669:0] info: server stats for thread 0: 53322 queries, 20319 answers from cache, 33003 recursions, 291 prefetch Jul 03 16:23:21 unbound[40669:0] info: server stats for thread 0: 55260 queries, 20697 answers from cache, 34563 recursions, 272 prefetch _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
