Very bad performance when copying large files from windows to samba-share

MCCALL,DON (HP-USA,ex1) don_mccall at hp.com
Mon Jun 24 11:45:38 GMT 2002


Hi Lars,
Just a guess, but what I see is a zero byte write request a offset 
719970304; a zero byte write request to an offset beyond the eof is
typically used by ms applications to 
'extend' a file, ie make sure physical space adequate for the entire
eventual operation is available before
writing data to the file.  if your OS is actually reserving this space by
writing 'zeros' to each and every
byte between 0 and 719970304, this could conceivably take a LONG time, and
explain the large time gap between
the zero byte write request, and the eventual RESPONSE to this request
approx. 45 seconds later.

Samba has a smb.conf parameter to deal with this called 'strict allocate' -
take a look at it in the man page
 for smb.conf.

Hope this helps,
Don
-----Original Message-----
From: Lars Heineken [mailto:Lars.Heineken at gmx.de]
Sent: Monday, June 24, 2002 14:19
To: samba-technical at lists.samba.org
Cc: ulf.bertilsson at adcomdata.no
Subject: Re: Very bad performance when copying large files from windows
to samba-share


This the summary:

Most interresting is the gap between the beginning of the transaction and
the actual writing (writing begins at about 45sec)
Any traffic above this point is just minor. After the 45sec the "real"
transfer begins.

As I found no way to search for checksum errors, I didn't found any..

The graph looks like this:

            --
          --
        --
-------|
       |      
.......45s

Or that in Bandwith:

       ######
       ------
       ######
       ------
-------|
       |
.......45s

I can attach screenshots if interested.

    No. Time        Source                Destination           Protocol
Info
      1 0.000000    lars-heineken.lan     192.168.10.255        CUPS
ipp://192.168.10.1:631/printers/HPLaserjet6L (idle)
      2 10.996660   www.heineken.lan      192.168.10.255        CUPS
ipp://heineken.lan:631/printers/HPLaserJet6L (idle)
      3 11.999360   lars-heineken.lan     arne-heineken.lan     TCP
hostname > boomerang [PSH, ACK] Seq=1926846500 Ack=1568123 Win=6432 Len=28
      4 12.009310   lars-heineken.lan     arne-heineken.lan     TCP
hostname > boomerang [PSH, ACK] Seq=1926846528 Ack=1568123 Win=6432 Len=36
      5 12.009479   arne-heineken.lan     lars-heineken.lan     TCP
boomerang > hostname [ACK] Seq=1568123 Ack=1926846564 Win=7704 Len=0
      6 13.987759   arne-heineken.lan     lars-heineken.lan     SMB
Tree Connect AndX Request, Path: \\LARS-HEINEKEN\IPC$
      7 13.989816   lars-heineken.lan     arne-heineken.lan     SMB
Tree Connect AndX Response
      8 13.990034   arne-heineken.lan     lars-heineken.lan     LANMAN
NetWkstaGetInfo Request
      9 13.990220   lars-heineken.lan     arne-heineken.lan     LANMAN
NetWkstaGetInfo Response
     10 13.990568   arne-heineken.lan     lars-heineken.lan     LANMAN
NetServerGetInfo Request
     11 13.990865   lars-heineken.lan     arne-heineken.lan     LANMAN
NetServerGetInfo Response
     12 13.991240   arne-heineken.lan     lars-heineken.lan     LANMAN
NetWkstaGetInfo Request
     13 13.991362   lars-heineken.lan     arne-heineken.lan     LANMAN
NetWkstaGetInfo Response
     14 13.992297   arne-heineken.lan     lars-heineken.lan     LANMAN
NetShareEnum Request
     15 13.992524   lars-heineken.lan     arne-heineken.lan     LANMAN
NetShareEnum Response
     16 13.993013   arne-heineken.lan     lars-heineken.lan     LANMAN
NetWkstaGetInfo Request
     17 13.993125   lars-heineken.lan     arne-heineken.lan     LANMAN
NetWkstaGetInfo Response
     18 14.045036   arne-heineken.lan     lars-heineken.lan     SMB
Open AndX Request, Path: \The Man Who Sued God (2001).XPD.ShareReactor.avi
     19 14.046435   lars-heineken.lan     arne-heineken.lan     SMB
Open AndX Response, FID: 0x1ba0
     20 14.046757   arne-heineken.lan     lars-heineken.lan     SMB
Write Request, FID: 0x1ba0, 0 bytes at offset 719970304, 0 bytes at offset
719970304
     21 14.079254   lars-heineken.lan     arne-heineken.lan     TCP
netbios-ssn > pe-mike [ACK] Seq=1974177356 Ack=1615097 Win=5840 Len=0
     22 15.895193   www.heineken.lan      192.168.10.255        RIPv1
Response
     23 16.048326   arne-heineken.lan     lars-heineken.lan     SMB
Transaction2 Request FIND_FIRST2, Pattern: \*
     24 16.048429   lars-heineken.lan     arne-heineken.lan     TCP
netbios-ssn > pe-mike [ACK] Seq=1974177356 Ack=1615182 Win=5840 Len=0
     25 16.173695   arne-heineken.lan     lars-heineken.lan     SMB
Tree Disconnect Request
     26 16.173765   lars-heineken.lan     arne-heineken.lan     TCP
netbios-ssn > pe-mike [ACK] Seq=1974177356 Ack=1615221 Win=5840 Len=0
     27 26.109439   lars-heineken.lan     192.168.10.255        BROWSER
Host Announcement LARS-HEINEKEN, Workstation, Server, Print Queue Server,
Xenix Server, NT Workstation, NT Server
     28 27.989388   lars-heineken.lan     192.168.10.255        CUPS
ipp://192.168.10.1:631/printers/HPDJ520 (idle)
     29 27.989448   lars-heineken.lan     192.168.10.255        CUPS
ipp://192.168.10.1:631/printers/lp (idle)
     30 30.989599   lars-heineken.lan     192.168.10.255        CUPS
ipp://192.168.10.1:631/printers/HPLaserjet6L (idle)
     31 41.977621   www.heineken.lan      192.168.10.255        CUPS
ipp://heineken.lan:631/printers/HPLaserJet6L (idle)
     32 45.886424   www.heineken.lan      192.168.10.255        RIPv1
Response
     33 57.336317   lars-heineken.lan     arne-heineken.lan     SMB
Write Response, 0 bytes
     34 57.345345   arne-heineken.lan     lars-heineken.lan     SMB
Write Request, FID: 0x1ba0, 65487 bytes at offset 0, 65487 bytes at offset 0
     35 57.345429   lars-heineken.lan     arne-heineken.lan     TCP
netbios-ssn > pe-mike [ACK] Seq=1974177397 Ack=1616681 Win=8760 Len=0
     36 57.345464   arne-heineken.lan     lars-heineken.lan     NBSS
NBSS Continuation Message
     37 57.345485   lars-heineken.lan     arne-heineken.lan     TCP
netbios-ssn > pe-mike [ACK] Seq=1974177397 Ack=1618141 Win=7300 Len=0
     38 57.345588   arne-heineken.lan     lars-heineken.lan     NBSS
NBSS Continuation Message
     39 57.345611  


On Mon, 24 Jun 2002 10:03:59 +0200
"Ulf Bertilsson" <ulf.bertilsson at adcomdata.no> wrote:

> > I did the ethereal-capturing. What looks very strange on 
> > first sight: About 6 of 10 packest are described as: NBSS 
> > Continuation Message.
> > Sometimes there are 6 of them one after another.
> > Is this normal ?
> 
> Lars,
> 
> Do you see any checksum errors in NBSS packet ?
> 
> If you use the TCP Stream Analysis in Ethereal,
> how to the graphs look ?
> 
> --
> Ulf
> 




More information about the samba-technical mailing list