From owner-freebsd-questions  Sun Aug  4 01:08:46 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id BAA20130
          for questions-outgoing; Sun, 4 Aug 1996 01:08:46 -0700 (PDT)
Received: from silver.sms.fi (root@silver.sms.fi [194.111.122.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA20122
          for <questions@freebsd.org>; Sun, 4 Aug 1996 01:08:38 -0700 (PDT)
Received: (from pete@localhost) by silver.sms.fi (8.7.5/8.6.9) id LAA12041; Sun, 4 Aug 1996 11:08:27 +0300 (EET DST)
Date: Sun, 4 Aug 1996 11:08:27 +0300 (EET DST)
Message-Id: <199608040808.LAA12041@silver.sms.fi>
From: Petri Helenius <pete@sms.fi>
To: Randy DuCharme <randyd@nconnect.net>
Cc: questions@freebsd.org
Subject: Samba file I/O performance
In-Reply-To: <32015C44.5358@nconnect.net>
References: <32015C44.5358@nconnect.net>
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Randy DuCharme writes:
 > Greetings,
 >    Are there any ways to improve the I/O performance of a Samba server.
 > File copies from DOS / Win95 stations seem slow compared to a similar
 > hardware configuration running NetWare or NT...or is this normal??
 > 
It's not. There is great document that accompanies samba telling you
about the tunning options, the one I've found useful is to put
socket options = TCP_NODELAY

in your smb.conf

ccd also helps you to push the performance further. We get 3.5 to 4
megabytes a second from the server per client over ATM NICs on the
win95 machines and 100 meg ethernet on the server. I think that's
pretty much the limit how much win95 can sustain.

Pete