From owner-freebsd-current@FreeBSD.ORG Wed Dec 4 16:26:30 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 59618B67 for ; Wed, 4 Dec 2013 16:26:30 +0000 (UTC) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2A3711DB0 for ; Wed, 4 Dec 2013 16:26:29 +0000 (UTC) Received: from Julian-MBP3.local (ppp121-45-246-96.lns20.per2.internode.on.net [121.45.246.96]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.7) with ESMTP id rB4GQOrr012482 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 4 Dec 2013 08:26:27 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <529F57AA.1000402@freebsd.org> Date: Thu, 05 Dec 2013 00:26:18 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: Shawn Webb , FreeBSD-current Subject: Re: unbound is extremely slow References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Dec 2013 16:26:30 -0000 On 12/4/13, 11:42 PM, Shawn Webb wrote: > So I have unbound running in a vnet jail. Doing a lookup with `host` is > pretty responsive, but Chromium's lookups are extremely slow (taking around > 30 seconds to resolve). I'm running pretty much a stock config. I've tried > turning off DNSSEC, but that doesn't help any. I have num-threads set to 4, > though I have 8 cores on this box. I've pasted my config below. get a Ktrace of the unbount process along with a a matching simultaneous tcpdump of whatever interface your packets are coming in through. by matching the incoming and outgoing packets with the socket activity, you should be able to isolate what component is taking all the time. > > Thanks, > > Shawn > > server: > username: unbound > directory: /var/unbound > chroot: /var/unbound > pidfile: /var/run/local_unbound.pid > #auto-trust-anchor-file: /var/unbound/root.key > logfile: /var/unbound/unbound.log > log-time-ascii: yes > log-queries: yes > verbosity: 2 > interface: 0.0.0.0 > interface: ::0 > access-control: 0.0.0.0/0 allow > access-control: ::0/0 allow > prefetch: yes > num-threads: 4 > > include: /var/unbound/forward.conf > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >