From owner-freebsd-current Thu Dec 13 10:39:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id DF48437B416 for ; Thu, 13 Dec 2001 10:39:07 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBDId7v70103; Thu, 13 Dec 2001 10:39:07 -0800 (PST) (envelope-from dillon) Date: Thu, 13 Dec 2001 10:39:07 -0800 (PST) From: Matthew Dillon Message-Id: <200112131839.fBDId7v70103@apollo.backplane.com> To: Luigi Rizzo Cc: current@FreeBSD.ORG Subject: Re: -current vs. -stable network performance References: <20011212224206.D35108@iguana.aciri.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've noticed that -current has much lower TCP performance. I haven't had time to investigate it but I presume there is some overhead somewhere that is killing it. -Matt :Hi, :I am testing the forwarding performance of CURRENT vs. STABLE :(both more or less up to date, unmodified, with the latest performance :patches to the "dc" driver, which I am using) and I am having some :surprises. : :STABLE can forward approx 125Kpps, whereas CURRENT tops at approx 80Kpps. : :This is on the same hardware, 750MHz Athlon, fastforwarding enabled, :a 4-port 21143 card, one input driven with a stream of up to 148Kpps :(64 bytes each). : :Ability to transmit seems roughly the same (in both cases 138Kpps), :and lack of CPU does not seem to be the problem (at least for :CURRENT), so I am suspecting some difference in the initialization :of PCI parameters, such as burst size etc, but I am unclear on :where to look at. Any ideas ? : : cheers : luigi :----------------------------------+----------------------------------------- : Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message