From owner-freebsd-isp Mon Apr 2 21:22: 2 2001 Delivered-To: freebsd-isp@freebsd.org Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (Postfix) with ESMTP id 38FAA37B722 for ; Mon, 2 Apr 2001 21:21:59 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 14kIGP-0002W9-00; Mon, 2 Apr 2001 21:17:53 -0700 Date: Mon, 2 Apr 2001 21:17:53 -0700 (PDT) From: Tom Samplonius To: Sean Chittenden Cc: freebsd-isp@freebsd.org Subject: Re: djbdns or tinydns In-Reply-To: <20010402211243.E53081@rand.tgd.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 2 Apr 2001, Sean Chittenden wrote: > This sounds like a kernel limit and not a dnscache limit as > I've run sites that were doing more than 200 requests per second and > never saw any problems.... have you tweaked your kernel at all? -sc No, 200 simultaneous UDP requests. It is a hardcoded limit in dnscache. Active UDP requests is the second to last number of the stats line in the main log. It can not exceed 200. I'm hopeful that code can be patched to bring it up to at least 250. There are no kernel limits that would affect requests per second. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message