From owner-freebsd-net@FreeBSD.ORG Fri Jan 16 02:30:24 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3252E1065670 for ; Fri, 16 Jan 2009 02:30:24 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from QMTA09.emeryville.ca.mail.comcast.net (qmta09.emeryville.ca.mail.comcast.net [76.96.30.96]) by mx1.freebsd.org (Postfix) with ESMTP id 19B898FC16 for ; Fri, 16 Jan 2009 02:30:24 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from OMTA02.emeryville.ca.mail.comcast.net ([76.96.30.19]) by QMTA09.emeryville.ca.mail.comcast.net with comcast id 40tk1b0010QkzPwA92ERQX; Fri, 16 Jan 2009 02:14:25 +0000 Received: from [192.168.1.104] ([71.57.105.220]) by OMTA02.emeryville.ca.mail.comcast.net with comcast id 42EP1b0094lKpr38N2EQak; Fri, 16 Jan 2009 02:14:25 +0000 Message-ID: <496FED82.3000303@tomjudge.com> Date: Thu, 15 Jan 2009 20:14:26 -0600 From: Tom Judge User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: jostb2345@yahoo.de References: <577907.44747.qm@web27006.mail.ukl.yahoo.com> In-Reply-To: <577907.44747.qm@web27006.mail.ukl.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-net@FreeBSD.org, freebsd-bugs@FreeBSD.org, vwe@FreeBSD.org Subject: Re: kern/96268: [socket] TCP socket performance drops by 3000% if packets are split at the first byte X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2009 02:30:24 -0000 Jost Boekemeier wrote: > Hi, > > from my point of view this issue can be closed. > > TCP write/write/read sequences are bad on any operating system, it's just that other OS are a little bit smarter. -- I think Jon Nagle has had a proposal to fix/remove this unconditional delay, but I don't know if it has been implemented. > > Furthermore this problem has been fixed on application level. And I think Patrick van Staveren maintains a FreeBSD port which uses unix domain- instead of TCP socket communication. > > > Regards, > Jost Bökemeier > Hi Jost, I'm not sure if Patrick (I work with him) has a port using unix domain sockets in production. I do know however that patches to PHP (That add the no delay socket option to the sockets API) where submitted after we found the work around for this issue and they where accepted. And that we have a patched php java bridge client running in production. My response was just to say that I have also seen this bug on a more recent release. Regards Tom