From owner-freebsd-hackers Thu Feb 4 16:05:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA18079 for freebsd-hackers-outgoing; Thu, 4 Feb 1999 16:05:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA18074 for ; Thu, 4 Feb 1999 16:05:54 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id QAA91618; Thu, 4 Feb 1999 16:05:42 -0800 (PST) (envelope-from dillon) Date: Thu, 4 Feb 1999 16:05:42 -0800 (PST) From: Matthew Dillon Message-Id: <199902050005.QAA91618@apollo.backplane.com> To: "Dirk-Willem van Gulik (vaio)" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Irratic Curve References: <36B97B38.74FF0B68@webweaving.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :... :http://www.scl.ameslab.gov/Projects/Gigabit/performance/prelim.html : :Now could any one explain to me WHY freebsd appears so unpredicatable ? :i.e. not a nice S-curve ? Is that the way of measuring ? Some other :artifact, or real ? I think it is real, as I get the same sort of :holes in my graphs for the transaction server. : :Any chances on an expose.... : :Dw If you want a transactional connection over TCP to go fast, you generally have to turn off nagle. { int one = 1; setsockopt(fd, IPPROTO_TCP, TCP_NODELAY, &one, sizeof(one)); } If the connection is pipelined, it can be a different story. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message