From owner-freebsd-hackers Wed Aug 12 13:46:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08026 for freebsd-hackers-outgoing; Wed, 12 Aug 1998 13:46:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from omnix.net (omnix.net [194.183.217.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA07983 for ; Wed, 12 Aug 1998 13:46:09 -0700 (PDT) (envelope-from didier@omnix.net) Received: from localhost (didier@localhost) by omnix.net (8.8.7/8.8.7) with SMTP id UAA23699; Wed, 12 Aug 1998 20:45:37 GMT (envelope-from didier@omnix.net) Date: Wed, 12 Aug 1998 22:45:37 +0200 (CEST) From: Didier Derny To: Remy NONNENMACHER cc: support@yard.de, hackers@FreeBSD.ORG Subject: Re: network problem with FreeBSD/Yard (yardnetd) In-Reply-To: <199808121144.MAA01217@bsd.synx.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 12 Aug 1998, Remy NONNENMACHER wrote: > > no, TCP_NODELAY allows your local stack to immediatly send packets to > peer without waiting for a ack. It's also called the Nagle algo. > It is intented for applications sending a lot of small packets. Delaying > send in this case is good since it allows the local stack to accumulate > data and build bigger pakets. > I did some testing with the ...ack_delayed=1 (not modified) and with the TCP_NODELAY forced in tcp_output.c (horrible hack) I obtained the same result and the database was really fast so, TCP_NODELAY could at least be a work around if Yard compiled a version of their program with this flag set. (actually the database is unusable 1 raw/s [without any hack]) but I'm not sure if it's the best solution By the way, I aslo did some testing with tcpblast on the loopback with ...ack_delayed=1 and without my awful hack on TCP_NODELAY I get a repeateable 30Mbs/s with ..ack_delayed=0 or the hack I get a very irregular result going from 2 to 30 Mb/s -- Didier Derny didier@omnix.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message