Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 11 Nov 2005 12:13:40 +0000 (GMT)
From:      Robert Watson <rwatson@FreeBSD.org>
To:        Joao Barros <joao.barros@gmail.com>
Cc:        freebsd-performance@freebsd.org, Jeremie Le Hen <jeremie@le-hen.org>
Subject:   Re: Poor Samba throughput on 6.0
Message-ID:  <20051111121144.P68007@fledge.watson.org>
In-Reply-To: <70e8236f0511090517g29b3f887x1b97ef5dec04548@mail.gmail.com>
References:  <70e8236f0511050457s5ce6d8batf805fbc9edd91360@mail.gmail.com> <20051109060931.GD5188@obiwan.tataz.chchile.org> <70e8236f0511090517g29b3f887x1b97ef5dec04548@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

On Wed, 9 Nov 2005, Joao Barros wrote:

> I tried using a single drive, an IDE and a SCSI-2 and on 2 machines at 
> work both with a RAID1. Even better, there is a part in my initial email 
> where I mention that having a 700MB file cached (iostat reported no 
> reads) the results were the same. With this in mind I don't think the 
> problem is at the storage level.

My feeling is that it is likely related to the network stack -- perhaps a 
combination of Samba<->sockets and TCP<->Windows, hence pointing at things 
like TCP settings.  It would be quite interesting to know what top -S 
looks like during (perhaps two minutes into) a long-haul transfer, and the 
output of systat -vmstat 1.  I know Apple has done some work on the 
efficiency of the FreeBSD SMB client when talking to windows servers 
relating to how TCP behaves, but haven't heard anything about them looking 
at similar issues in Samba.

Robert N M Watson



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051111121144.P68007>