ory and cache-min-ttl are large enough.
Vinay.
From: Stephan Lagerholm [mailto:stephan.lagerh...@secure64.com]
Sent: Monday, July 09, 2012 6:35 AM
To: vin...@justemail.net; unbound-users@unbound.net
Subject: RE: [Unbound-users] Improve avg response times
Hi Vinay,
The unbound name ser
, July 07, 2012 1:55 PM
To: unbound-users@unbound.net
Subject: Re: [Unbound-users] Improve avg response times
I tried using a prefetch trigger at 90% instead of 10% (intentionally
inefficient) and a cache-min-ttl of 5400 so that an hourly scan is
guaranteed to find a cached entry from the las
I tried using a prefetch trigger at 90% instead of 10% (intentionally
inefficient) and a cache-min-ttl of 5400 so that an hourly scan is
guaranteed to find a cached entry from the last scan and will also reset
it's TTL back to 5400 by forcing a new iteration.
If I do a new namebench run, I stil
I am using an amazon large EC2 instance (4ECUs, 2 cores) for my unbound
configured as below. I am seeing a 150ms+ average response time as reported
by namebench Alexa 2K result. In order to reduce my lookup times, I am
running an hourly scan of these 35K sites (from namebench dat files) in
order to
