From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 2 12:55:21 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B225B1065773; Thu, 2 Sep 2010 12:55:21 +0000 (UTC) (envelope-from des@des.no) Received: from smtp.des.no (smtp.des.no [194.63.250.102]) by mx1.freebsd.org (Postfix) with ESMTP id 728548FC1A; Thu, 2 Sep 2010 12:55:21 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id AD73C1FFC37; Thu, 2 Sep 2010 12:55:20 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 745318457B; Thu, 2 Sep 2010 14:55:20 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Alexander Best References: <20100831180103.GA92584@freebsd.org> <86fwxt5ng1.fsf@ds4.des.no> <20100901222834.GA66517@freebsd.org> <864oe8mpga.fsf@ds4.des.no> <20100902114655.GA9071@freebsd.org> <8639tsl5q0.fsf@ds4.des.no> <20100902122348.GA38047@freebsd.org> Date: Thu, 02 Sep 2010 14:55:20 +0200 In-Reply-To: <20100902122348.GA38047@freebsd.org> (Alexander Best's message of "Thu, 2 Sep 2010 12:23:48 +0000") Message-ID: <86pqwwjoef.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: expand_number() for fetch'es -B and -S switches X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Sep 2010 12:55:21 -0000 Alexander Best writes: > the current maximum buffer limit of fetch(1) actually is around 1G. i > think 1M is not enough, because if people are pulling data over fast > lines they'll have almost constant disk writes. how about 100M then? > ;) Large buffer sizes are *not* better, since fetch(1) will alternate between filling the buffer and writing it to disk. The buffer should not be too small, but it should not be too large either; the sweet spot is somewhere around 128 kB. > on the other hand why have a maximum limit? if people want to have a > buffer of 100 gigabyte why shouldn't they? it's their decision > actually. Good point... although if they set it too high, either malloc(3) will fail - if they're lucky - or fetch(1) will crash when the system runs out of physical RAM and swap, and they'll have to start over. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no