samba - Apr 2006 - Big performance difference between smbclient put/get

Hi list,

I'm using Samba 3.0.21 on a FC4 box.

When copying files using smbclient I get huge speed differences  
between put and get commands.

smb: \> put backup.tar
putting file backup.tar as \backup.tar (543.0 kb/s) (average 543.0 kb/s)
smb: \> get backup.tar
getting file \backup.tar of size 31549440 as backup.tar (7681.4 kb/s)  
(average 7681.4 kb/s)
smb: \> put backup.tar
putting file backup.tar as \backup.tar (512.5 kb/s) (average 527.3 kb/s)
smb: \>


Get => 7681.4 kb/s
Put => 530 kb/s

Any reason why?

Cheers,
Henrik

henke@mac.se wrote:
> Hi list,
> 
> I'm using Samba 3.0.21 on a FC4 box.
> 
> When copying files using smbclient I get huge speed differences between 
> put and get commands.
> 
> smb: \> put backup.tar
> putting file backup.tar as \backup.tar (543.0 kb/s) (average 543.0 kb/s)
> smb: \> get backup.tar
> getting file \backup.tar of size 31549440 as backup.tar (7681.4 kb/s) 
> (average 7681.4 kb/s)
> smb: \> put backup.tar
> putting file backup.tar as \backup.tar (512.5 kb/s) (average 527.3 kb/s)
> smb: \>
> 
> 
> Get => 7681.4 kb/s
> Put => 530 kb/s
> 
> Any reason why?
> 
Any idea how your socket buffers are set in smb.conf? That can make a 
huge difference in my experience. so_rcvbuf and so_sndbuf

On 4/13/06, Henrik Zagerholm <henke@mac.se> wrote:
> Hi list,
>
> I'm using Samba 3.0.21 on a FC4 box.
>
> When copying files using smbclient I get huge speed differences
> between put and get commands.
>
> smb: \> put backup.tar
> putting file backup.tar as \backup.tar (543.0 kb/s) (average 543.0 kb/s)
> smb: \> get backup.tar
> getting file \backup.tar of size 31549440 as backup.tar (7681.4 kb/s)
> (average 7681.4 kb/s)
> smb: \> put backup.tar
> putting file backup.tar as \backup.tar (512.5 kb/s) (average 527.3 kb/s)
> smb: \>
>
>
> Get => 7681.4 kb/s
> Put => 530 kb/s
>
> Any reason why?
Could be anything. In general, there is no reason to expect reads and
writes to achieve thta same bandwidth, and a mixed read/write workload
will be different again. The reasons for this particular result could
be in smbclient or they could be in the I/O stack on the server or the
client.

--
James Peach | jorgar@gmail.com