From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 21 21:06:27 2009 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 226F11065698 for ; Mon, 21 Dec 2009 21:06:27 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-ew0-f211.google.com (mail-ew0-f211.google.com [209.85.219.211]) by mx1.freebsd.org (Postfix) with ESMTP id 916698FC19 for ; Mon, 21 Dec 2009 21:06:26 +0000 (UTC) Received: by ewy3 with SMTP id 3so6537327ewy.13 for ; Mon, 21 Dec 2009 13:06:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=EkV2tVJAU/Qp0F/eiFGQxKVzxQEbzaUVL9gmBh/tpp4=; b=b/wX6nZ/56imizXDp0CwC89ssmoMbeTaaY4AY9g7L58fCMhna9ccPntmfLK5wOew0e ry8vXYXsaRHjwxM0rUc1wxvQE8IvNyYpglFGhC8P0mT0Z0tIje5w70yODCmNvsnPuT2k WCiux6UmwDhzhuxPG3A8WyrJtB3pjFzTLYsXk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=dQK47wgn0XPx/99MGW5JTv3BCL3Ql/9GWVBRHSIkszpkQW0TH+dEGtDJE7kUpRg8X8 Tlt9wvKUAwiCq006ROcyvEg9a0Avf3Ap7PDNcnQF0fIY8rJbOREXCoZZo9JqNdEvjpI+ crm8gCGM4tO6LXufuhCwQt37Tot3W5ZD9+HmE= MIME-Version: 1.0 Received: by 10.216.87.194 with SMTP id y44mr2675654wee.204.1261429585209; Mon, 21 Dec 2009 13:06:25 -0800 (PST) In-Reply-To: <200912212042.nBLKga0G021550@apollo.backplane.com> References: <5f67a8c40912182147t1adc158ew9fd3d94c4c4c955f@mail.gmail.com> <200912212042.nBLKga0G021550@apollo.backplane.com> Date: Mon, 21 Dec 2009 16:06:25 -0500 Message-ID: <5f67a8c40912211306k657b9a2aj7c037d3f08b8ab21@mail.gmail.com> From: Zaphod Beeblebrox To: Matthew Dillon Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: scp more perfectly fills the pipe than NFS/TCP 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: Mon, 21 Dec 2009 21:06:27 -0000 I must say that I often deeply respect your position and your work, but your recent willingness to jump into a conversation without reading the whole of it ... simply to point out some point where your pet is better than the subject of the list... is disappointing. Case in point... On Mon, Dec 21, 2009 at 3:42 PM, Matthew Dillon wrote: > =A0 =A0Play with the read-ahead mount options for NFS, but it might requi= re > =A0 =A0more work with that kind of latency. =A0You need to be able to hav= e > =A0 =A0a lot of RPC's in-flight to maintain the pipeline with higher late= ncies. > =A0 =A0At least 16 and possibly more. I should almost label that ObContent. > =A0 =A0It might be easier to investigate why the latency is so high and f= ix > =A0 =A0that first. =A010ms is way too high for a LAN. Ref. my origional post. The connection is DSL, but completely managed. 10ms is fairly good for DSL > =A0 =A0Make sure the NFS mount is TCP (It defaults to TCP in FreeBSD 8+).= =A0UDP > =A0 =A0mounts will not perform well with any read-ahead greater then 3 or= 4 > =A0 =A0RPCs because occassional seek latencies on the server will cause > =A0 =A0random UDP RPCs to timeout and retry, which completely destroys > =A0 =A0performance. =A0UDP mounts have no understanding of the RPC queue = backlog > =A0 =A0on the server and treat each RPC independently for timeout/retry > =A0 =A0purposes. =A0So one minor stall can blow up every single pending R= PC > =A0 =A0backed up behind the one that stalled. Again, from the original post, not only was -T specified, but (as you say) it is the default for FreeBSD 8. for a 4 megabit pipe, very few transactions need to be in flight to fill it. Does the TCP NFS use tech like selective ack? Is it the same stack as the one that scp is using?