Re: [Samba] Client link utilization
On Fri, Feb 26, 2010 at 02:13:45PM +0100, Diego Zuccato wrote: > Volker Lendecke wrote: > >>> smbclient pulling data from WinXP => ~4MB/s >>> 2xsmbclient pulling data from WinXP => ~8MB/s >>> 3xsmbclient pulling data from WinXP => ~11MB/s >> Which smbclient version? > Last time I tested I was using 2.4.2. I'll try again with 2.4.3 ASAP. Assuming you mean 3.4.2, there is definitely something fishy. Very difficult to diagnose without access to your box though, sorry. Volker signature.asc Description: Digital signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Client link utilization
Volker Lendecke wrote: smbclient pulling data from WinXP => ~4MB/s 2xsmbclient pulling data from WinXP => ~8MB/s 3xsmbclient pulling data from WinXP => ~11MB/s Which smbclient version? Last time I tested I was using 2.4.2. I'll try again with 2.4.3 ASAP. -- Diego Zuccato Servizi Informatici Dip. di Astronomia - Università di Bologna Via Ranzani, 1 - 40126 Bologna - Italy tel.: +39 051 20 95786 mail: diego.zucc...@unibo.it -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Client link utilization
On Fri, Feb 26, 2010 at 10:06:28AM +0100, Diego Zuccato wrote: > >Am I correct in saying: > > > >smbclient -> smbd maxes the wire. > >smbclient -> WinXP maxes the wire. > Not in my case. I noticed that > smbclient pulling data from WinXP => ~4MB/s > 2xsmbclient pulling data from WinXP => ~8MB/s > 3xsmbclient pulling data from WinXP => ~11MB/s Which smbclient version? Volker pgpJ03kAvVK0t.pgp Description: PGP signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Client link utilization
Jeremy Allison wrote: Am I correct in saying: smbclient -> smbd maxes the wire. smbclient -> WinXP maxes the wire. Not in my case. I noticed that smbclient pulling data from WinXP => ~4MB/s 2xsmbclient pulling data from WinXP => ~8MB/s 3xsmbclient pulling data from WinXP => ~11MB/s -- Diego Zuccato Servizi Informatici Dip. di Astronomia - Università di Bologna Via Ranzani, 1 - 40126 Bologna - Italy tel.: +39 051 20 95786 mail: diego.zucc...@unibo.it -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Client link utilization
This is not the whole truth. With smbclient command line tool I have the same exact problem (max 3,8MB/s). b. On 9 February 2010 17:19, Jeremy Allison wrote: > On Tue, Feb 09, 2010 at 10:25:44AM -0500, Lennart Sorensen wrote: >> On Tue, Feb 09, 2010 at 01:19:40AM +0100, Bostjan Skufca wrote: >> > Then I am greedier (if I also strive for 11MB/s:) Thanks for reminding >> > me though. >> > >> > Can/Did someone push it over 10MB/s (or 100MB/s with 1Gbps ethernet))? >> > >> > >> > To Jeremy or someone who is involved in samba as a developer: do any >> > particular kernel options influence performance of smbclient, that you >> > know of? Compile time options? Compiler version? >> >> Well I just checked what settings my NFS mount that works great is using. >> it uses: >> rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600, >> retrans=2,sec=sys,mountvers=3,mountproto=udp >> >> Now I tried different rsize values with cifs as well, but that doesn't >> seem to help (at least 64k made no improvement. Going down to 4k made >> it slower). >> >> Looking at it carefully, it turns out trying to set it over 16k gets >> ignored. Changing the option CIFSMaxBufSize on the cifs module to 130048, >> does allow using rsize up to that value, and the speed goes up to 8.3MB/s >> from 7.5MB/s. So it seems larger rsize makes it better. Given nfs uses >> 8 times larger yet and gets great speed may be a clue too. > > There are two issues here. One is the problem with the > Linux CIFSFS which you're talking about. FYI. Samba is > able to cope with single request read/write sizes up to > 16MB from a UNIX extension client (smbclient can do this) > so you might want to talk to Steve French to learn how > to turn this on. > > The second issue is the one with Windows clients. As > the redirectors are completely different, with completely > different requests and semantics I'd rather not get the > two confused in this thread. Please split out another > mailing list thread for the CIFSFS client speed issue, > so we have them clearly separated. > > Jeremy. > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Client link utilization
On Tue, Feb 09, 2010 at 10:25:44AM -0500, Lennart Sorensen wrote: > On Tue, Feb 09, 2010 at 01:19:40AM +0100, Bostjan Skufca wrote: > > Then I am greedier (if I also strive for 11MB/s:) Thanks for reminding > > me though. > > > > Can/Did someone push it over 10MB/s (or 100MB/s with 1Gbps ethernet))? > > > > > > To Jeremy or someone who is involved in samba as a developer: do any > > particular kernel options influence performance of smbclient, that you > > know of? Compile time options? Compiler version? > > Well I just checked what settings my NFS mount that works great is using. it > uses: > rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600, > retrans=2,sec=sys,mountvers=3,mountproto=udp > > Now I tried different rsize values with cifs as well, but that doesn't > seem to help (at least 64k made no improvement. Going down to 4k made > it slower). > > Looking at it carefully, it turns out trying to set it over 16k gets > ignored. Changing the option CIFSMaxBufSize on the cifs module to 130048, > does allow using rsize up to that value, and the speed goes up to 8.3MB/s > from 7.5MB/s. So it seems larger rsize makes it better. Given nfs uses > 8 times larger yet and gets great speed may be a clue too. There are two issues here. One is the problem with the Linux CIFSFS which you're talking about. FYI. Samba is able to cope with single request read/write sizes up to 16MB from a UNIX extension client (smbclient can do this) so you might want to talk to Steve French to learn how to turn this on. The second issue is the one with Windows clients. As the redirectors are completely different, with completely different requests and semantics I'd rather not get the two confused in this thread. Please split out another mailing list thread for the CIFSFS client speed issue, so we have them clearly separated. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Client link utilization
On Tue, Feb 09, 2010 at 01:19:40AM +0100, Bostjan Skufca wrote: > Then I am greedier (if I also strive for 11MB/s:) Thanks for reminding > me though. > > Can/Did someone push it over 10MB/s (or 100MB/s with 1Gbps ethernet))? > > > To Jeremy or someone who is involved in samba as a developer: do any > particular kernel options influence performance of smbclient, that you > know of? Compile time options? Compiler version? Well I just checked what settings my NFS mount that works great is using. it uses: rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600, retrans=2,sec=sys,mountvers=3,mountproto=udp Now I tried different rsize values with cifs as well, but that doesn't seem to help (at least 64k made no improvement. Going down to 4k made it slower). Looking at it carefully, it turns out trying to set it over 16k gets ignored. Changing the option CIFSMaxBufSize on the cifs module to 130048, does allow using rsize up to that value, and the speed goes up to 8.3MB/s from 7.5MB/s. So it seems larger rsize makes it better. Given nfs uses 8 times larger yet and gets great speed may be a clue too. -- Len Sorensen -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Client link utilization
Then I am greedier (if I also strive for 11MB/s:) Thanks for reminding me though. Can/Did someone push it over 10MB/s (or 100MB/s with 1Gbps ethernet))? To Jeremy or someone who is involved in samba as a developer: do any particular kernel options influence performance of smbclient, that you know of? Compile time options? Compiler version? Thanks again, b. On 9 February 2010 00:32, Stan Hoeppner wrote: > Bostjan Skufca put forth on 2/8/2010 4:07 PM: >> Thanks! >> >> "We have a bidder at 7,5 MB/s, do I hear more? Do we have 8 MB/s?" :) > > 8.5MB/s here from both (an old) smbclient and Winders 2K/XP. But, of course, > you already knew that from my previous posts. Just getting it into this > thread > for your tally. I'm hoping I can eventually figure out how to get wire speed > out of smbd 3.2.5, or Debian's successor rev. I kinda feel greedy, with you > only getting ~4MB/s and me [demanding] 11MB/s. :( > > -- > Stan > > >> On 8 February 2010 21:27, Lennart Sorensen >> wrote: >>> On Mon, Feb 08, 2010 at 08:53:11PM +0100, Bostjan Skufca wrote: Ok, a quick questions for everyone: Can you max a 100Mbps ethernet connection to SMBD server using smbclient or mount.cifs? What transfer speeds can you reach? 8MB/s, 10MB/s, 11,5MB/s? Thanks everybody, b. PS: Because if you can and I can't, that means only I have a client side problem. >>> >>> Well using a 100Mbit connection, nfs gives me 11.3MB/s and using cifs >>> gives me 7.5MB/s. Same file from same server to the same client using >>> rsync --progress to show the transfer rate of receiving from the server. >>> >>> Samba 3.4.2 on the server. >>> >>> -- >>> Len Sorensen >>> > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Client link utilization
Bostjan Skufca put forth on 2/8/2010 4:07 PM: > Thanks! > > "We have a bidder at 7,5 MB/s, do I hear more? Do we have 8 MB/s?" :) 8.5MB/s here from both (an old) smbclient and Winders 2K/XP. But, of course, you already knew that from my previous posts. Just getting it into this thread for your tally. I'm hoping I can eventually figure out how to get wire speed out of smbd 3.2.5, or Debian's successor rev. I kinda feel greedy, with you only getting ~4MB/s and me [demanding] 11MB/s. :( -- Stan > On 8 February 2010 21:27, Lennart Sorensen > wrote: >> On Mon, Feb 08, 2010 at 08:53:11PM +0100, Bostjan Skufca wrote: >>> Ok, a quick questions for everyone: >>> >>> Can you max a 100Mbps ethernet connection to SMBD server using >>> smbclient or mount.cifs? >>> >>> What transfer speeds can you reach? 8MB/s, 10MB/s, 11,5MB/s? >>> >>> Thanks everybody, >>> b. >>> >>> PS: Because if you can and I can't, that means only I have a client >>> side problem. >> >> Well using a 100Mbit connection, nfs gives me 11.3MB/s and using cifs >> gives me 7.5MB/s. Same file from same server to the same client using >> rsync --progress to show the transfer rate of receiving from the server. >> >> Samba 3.4.2 on the server. >> >> -- >> Len Sorensen >> -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Client link utilization
Thanks! "We have a bidder at 7,5 MB/s, do I hear more? Do we have 8 MB/s?" :) b. On 8 February 2010 21:27, Lennart Sorensen wrote: > On Mon, Feb 08, 2010 at 08:53:11PM +0100, Bostjan Skufca wrote: >> Ok, a quick questions for everyone: >> >> Can you max a 100Mbps ethernet connection to SMBD server using >> smbclient or mount.cifs? >> >> What transfer speeds can you reach? 8MB/s, 10MB/s, 11,5MB/s? >> >> Thanks everybody, >> b. >> >> PS: Because if you can and I can't, that means only I have a client >> side problem. > > Well using a 100Mbit connection, nfs gives me 11.3MB/s and using cifs > gives me 7.5MB/s. Same file from same server to the same client using > rsync --progress to show the transfer rate of receiving from the server. > > Samba 3.4.2 on the server. > > -- > Len Sorensen > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Client link utilization
On Mon, Feb 08, 2010 at 08:53:11PM +0100, Bostjan Skufca wrote: > Ok, a quick questions for everyone: > > Can you max a 100Mbps ethernet connection to SMBD server using > smbclient or mount.cifs? > > What transfer speeds can you reach? 8MB/s, 10MB/s, 11,5MB/s? > > Thanks everybody, > b. > > PS: Because if you can and I can't, that means only I have a client > side problem. Well using a 100Mbit connection, nfs gives me 11.3MB/s and using cifs gives me 7.5MB/s. Same file from same server to the same client using rsync --progress to show the transfer rate of receiving from the server. Samba 3.4.2 on the server. -- Len Sorensen -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Client link utilization
Ok, a quick questions for everyone: Can you max a 100Mbps ethernet connection to SMBD server using smbclient or mount.cifs? What transfer speeds can you reach? 8MB/s, 10MB/s, 11,5MB/s? Thanks everybody, b. PS: Because if you can and I can't, that means only I have a client side problem. On 7 February 2010 19:53, Bostjan Skufca wrote: > My case is slightly different. Only 2 combinations are interesting > when compared: > 1. WinXXX client ---> smbd (max) > 2. smbclient ---> smbd (1/3) > > The first combo maxes the wire with only 1 client connected, in any > direction (GET/PUT). > The second, however, seems to work at 1/3 of wire speed. Direction > again does not matter. > (talking about large files and sustained transfer rates here). > > In the second combination the network stack 'seems' ok because FTP, > HTTP and SCP transfers do max out the wire. It also makes no > difference if I use smbclient from command line or mount.cifs > variation, always 1/3 of line capacity. > > I have just checked if this is still the case with latest samba > version. I used Samba 3.4.5 compiled from source (source3 directory) > on both client and server. The issue still persist. > > Thanks for taking interest! > b. > > > > On 7 February 2010 10:40, Stan Hoeppner wrote: >> Jeremy Allison put forth on 2/6/2010 11:07 PM: >>> On Sat, Feb 06, 2010 at 09:26:32PM -0600, Stan Hoeppner wrote: Bostjan Skufca put forth on 2/6/2010 6:14 PM: > Hello everybody! > > This is probably going to be a classic question but I cannot find a > decent answer on net. > > I have samba server set up and the following things work flawlessly: > - iperf shows 92% link utilization > - FTP/SCP/HTTP transfers work in 10MB/s range. > > However, when I mount samba share with linux client (mount.cifs) the > link utilization cannot bypass cca 33%. Transfer speeds constantly > stops around 3.8MB/s and will not rise above it no matter what socket > and locking options I use. > > Do you have any ideas about why this is happening and/or FAQ websites > to point me to? I've had a similar thread running for a few weeks without resolution. In my case I can max the wire (100FDX) at 92Mb/s to/from Win2K and WinXP clients using FTP, and smbclient from the server to shares on the workstations maxes the wire (at least GET from the workstations does). I'm running Samba 3.2.5 on Debian Lenny with custom kernel 2.6.31.1. The max smb performance I can get in a single stream to/from smbd is 65Mb/s, or 8.5MB/s. I've now tested Win2K, WinXP, and smbclient on SLED 10 (can't recall version). In all cases, no matter what performance settings I tweak in smb.conf or on the workstations, I can't get wire speed with a single SMB stream---can't get over 65Mb/s. Interestingly, two simultaneous SMB transfer streams (two Windows Explorer file copy operations on the same workstation) will max the wire at 92Mb/s, or 11MB/s. >>> >>> Hang on a minute, I haven't been paying attention to these emails >>> as yet. >> >> >> Thanks for jumping in Jeremy. >> >>> Am I correct in saying: >> >> Partially. Before I forget, let me state I'm only speaking for my case, not >> the >> other OP with a similar issue, whose thread this is. >> >>> smbclient -> smbd maxes the wire. >> >> This is not correct. SLED 10's smbclient (2006'ish, not sure of version) >> gets >> 2/3 wire speed to/from the smbd server, Debian Lenny Samba 3.2.5. In this >> case, >> it's seeing exactly the same single stream performance as the Windows >> clients. >> >>> smbclient -> WinXP maxes the wire. >> >> Yes, smbclient 3.2.5 on the Debian Lenny smbd server can GET from WinXP and >> Win2K at wire speed, however, PUT ops are half wire speed, 6MB/s. I haven't >> attempted to troubleshoot this half speed issue yet. >> >>> But WinXP -> smbd gets 2/3 of the wire speed. >> >> Correct. Win2K and WinXP both achieve 2/3 wire speed to/from smbd. >> >>> And WinXP+WinXP (two streams) -> smbd maxes the wire. >> >> Correct, but mostly tested from a Win2K machine, not XP. Just to be clear, >> this >> is two streams from one Windows host. Two concurrent file copy ops from two >> shares on the smbd server, and this maxes the wire every time. >> >>> If this is the case, it's the 64k per read/write >>> limit plus only one outstanding packet per stream >>> issue with the WinXP redirector that's the issue. >> >> Hmm. If this is the case, why do the Win hosts nearly max the wire talking >> smb >> to one another, at ~10.5MB/s, and max the wire serving files to smbclient on >> the >> Linux server host? >> >>> smbclient sends up to maxmux outstanding packets >>> on read/write and keeps the pipeline full. That's >>> why it can max the wire. >> >> Well, smbclient 3.2.5 maxes the wire GETing from the Windows hots' shares, >> but
Re: [Samba] Client link utilization
My case is slightly different. Only 2 combinations are interesting when compared: 1. WinXXX client ---> smbd(max) 2. smbclient---> smbd(1/3) The first combo maxes the wire with only 1 client connected, in any direction (GET/PUT). The second, however, seems to work at 1/3 of wire speed. Direction again does not matter. (talking about large files and sustained transfer rates here). In the second combination the network stack 'seems' ok because FTP, HTTP and SCP transfers do max out the wire. It also makes no difference if I use smbclient from command line or mount.cifs variation, always 1/3 of line capacity. I have just checked if this is still the case with latest samba version. I used Samba 3.4.5 compiled from source (source3 directory) on both client and server. The issue still persist. Thanks for taking interest! b. On 7 February 2010 10:40, Stan Hoeppner wrote: > Jeremy Allison put forth on 2/6/2010 11:07 PM: >> On Sat, Feb 06, 2010 at 09:26:32PM -0600, Stan Hoeppner wrote: >>> Bostjan Skufca put forth on 2/6/2010 6:14 PM: Hello everybody! This is probably going to be a classic question but I cannot find a decent answer on net. I have samba server set up and the following things work flawlessly: - iperf shows 92% link utilization - FTP/SCP/HTTP transfers work in 10MB/s range. However, when I mount samba share with linux client (mount.cifs) the link utilization cannot bypass cca 33%. Transfer speeds constantly stops around 3.8MB/s and will not rise above it no matter what socket and locking options I use. Do you have any ideas about why this is happening and/or FAQ websites to point me to? >>> >>> I've had a similar thread running for a few weeks without resolution. In my >>> case I can max the wire (100FDX) at 92Mb/s to/from Win2K and WinXP clients >>> using >>> FTP, and smbclient from the server to shares on the workstations maxes the >>> wire >>> (at least GET from the workstations does). I'm running Samba 3.2.5 on >>> Debian >>> Lenny with custom kernel 2.6.31.1. >>> >>> The max smb performance I can get in a single stream to/from smbd is >>> 65Mb/s, or >>> 8.5MB/s. I've now tested Win2K, WinXP, and smbclient on SLED 10 (can't >>> recall >>> version). In all cases, no matter what performance settings I tweak in >>> smb.conf >>> or on the workstations, I can't get wire speed with a single SMB >>> stream---can't >>> get over 65Mb/s. >>> >>> Interestingly, two simultaneous SMB transfer streams (two Windows Explorer >>> file >>> copy operations on the same workstation) will max the wire at 92Mb/s, or >>> 11MB/s. >> >> Hang on a minute, I haven't been paying attention to these emails >> as yet. > > > Thanks for jumping in Jeremy. > >> Am I correct in saying: > > Partially. Before I forget, let me state I'm only speaking for my case, not > the > other OP with a similar issue, whose thread this is. > >> smbclient -> smbd maxes the wire. > > This is not correct. SLED 10's smbclient (2006'ish, not sure of version) gets > 2/3 wire speed to/from the smbd server, Debian Lenny Samba 3.2.5. In this > case, > it's seeing exactly the same single stream performance as the Windows clients. > >> smbclient -> WinXP maxes the wire. > > Yes, smbclient 3.2.5 on the Debian Lenny smbd server can GET from WinXP and > Win2K at wire speed, however, PUT ops are half wire speed, 6MB/s. I haven't > attempted to troubleshoot this half speed issue yet. > >> But WinXP -> smbd gets 2/3 of the wire speed. > > Correct. Win2K and WinXP both achieve 2/3 wire speed to/from smbd. > >> And WinXP+WinXP (two streams) -> smbd maxes the wire. > > Correct, but mostly tested from a Win2K machine, not XP. Just to be clear, > this > is two streams from one Windows host. Two concurrent file copy ops from two > shares on the smbd server, and this maxes the wire every time. > >> If this is the case, it's the 64k per read/write >> limit plus only one outstanding packet per stream >> issue with the WinXP redirector that's the issue. > > Hmm. If this is the case, why do the Win hosts nearly max the wire talking > smb > to one another, at ~10.5MB/s, and max the wire serving files to smbclient on > the > Linux server host? > >> smbclient sends up to maxmux outstanding packets >> on read/write and keeps the pipeline full. That's >> why it can max the wire. > > Well, smbclient 3.2.5 maxes the wire GETing from the Windows hots' shares, but > only hits 1/2 wire speed on PUT ops to the Windows shares. SLED 10 smbclient > only reaches 2/3 wire speed <-> smbd on the Debian Samba server, although I > didn't test SLED 10 smbclient against the Windows hosts. > >> The WinXP redirector is just not very good I'm >> afraid. > > That may be true. But I'd be remiss if I didn't point out that XP is one of > two > machines I have which can actually serve single stream smb at wire speed. The > other, sadly, is Win2K. Both can serve smb to smbc
Re: [Samba] Client link utilization
On Sat, Feb 06, 2010 at 09:26:32PM -0600, Stan Hoeppner wrote: > Bostjan Skufca put forth on 2/6/2010 6:14 PM: > > Hello everybody! > > > > This is probably going to be a classic question but I cannot find a > > decent answer on net. > > > > I have samba server set up and the following things work flawlessly: > > - iperf shows 92% link utilization > > - FTP/SCP/HTTP transfers work in 10MB/s range. > > > > However, when I mount samba share with linux client (mount.cifs) the > > link utilization cannot bypass cca 33%. Transfer speeds constantly > > stops around 3.8MB/s and will not rise above it no matter what socket > > and locking options I use. > > > > Do you have any ideas about why this is happening and/or FAQ websites > > to point me to? > > I've had a similar thread running for a few weeks without resolution. In my > case I can max the wire (100FDX) at 92Mb/s to/from Win2K and WinXP clients > using > FTP, and smbclient from the server to shares on the workstations maxes the > wire > (at least GET from the workstations does). I'm running Samba 3.2.5 on Debian > Lenny with custom kernel 2.6.31.1. > > The max smb performance I can get in a single stream to/from smbd is 65Mb/s, > or > 8.5MB/s. I've now tested Win2K, WinXP, and smbclient on SLED 10 (can't recall > version). In all cases, no matter what performance settings I tweak in > smb.conf > or on the workstations, I can't get wire speed with a single SMB > stream---can't > get over 65Mb/s. > > Interestingly, two simultaneous SMB transfer streams (two Windows Explorer > file > copy operations on the same workstation) will max the wire at 92Mb/s, or > 11MB/s. Hang on a minute, I haven't been paying attention to these emails as yet. Am I correct in saying: smbclient -> smbd maxes the wire. smbclient -> WinXP maxes the wire. But WinXP -> smbd gets 2/3 of the wire speed. And WinXP+WinXP (two streams) -> smbd maxes the wire. If this is the case, it's the 64k per read/write limit plus only one outstanding packet per stream issue with the WinXP redirector that's the issue. smbclient sends up to maxmux outstanding packets on read/write and keeps the pipeline full. That's why it can max the wire. The WinXP redirector is just not very good I'm afraid. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Client link utilization
Yes, I've forgot to mention that I can also get link saturated with single Win client, therefore it does not appear to be a server issue. BTW: Slack, samba compiled from scratch (v3.4.5) and custom vanilla kernel (but nothing fancy or unusual). b. PS: The funny thing is, as I recall, I did previous samba setup 5 or 6 years ago, and I distinclty remember I was running into the same issue, at more or less the same speed. On 7 February 2010 04:26, Stan Hoeppner wrote: > Bostjan Skufca put forth on 2/6/2010 6:14 PM: >> Hello everybody! >> >> This is probably going to be a classic question but I cannot find a >> decent answer on net. >> >> I have samba server set up and the following things work flawlessly: >> - iperf shows 92% link utilization >> - FTP/SCP/HTTP transfers work in 10MB/s range. >> >> However, when I mount samba share with linux client (mount.cifs) the >> link utilization cannot bypass cca 33%. Transfer speeds constantly >> stops around 3.8MB/s and will not rise above it no matter what socket >> and locking options I use. >> >> Do you have any ideas about why this is happening and/or FAQ websites >> to point me to? > > I've had a similar thread running for a few weeks without resolution. In my > case I can max the wire (100FDX) at 92Mb/s to/from Win2K and WinXP clients > using > FTP, and smbclient from the server to shares on the workstations maxes the > wire > (at least GET from the workstations does). I'm running Samba 3.2.5 on Debian > Lenny with custom kernel 2.6.31.1. > > The max smb performance I can get in a single stream to/from smbd is 65Mb/s, > or > 8.5MB/s. I've now tested Win2K, WinXP, and smbclient on SLED 10 (can't recall > version). In all cases, no matter what performance settings I tweak in > smb.conf > or on the workstations, I can't get wire speed with a single SMB > stream---can't > get over 65Mb/s. > > Interestingly, two simultaneous SMB transfer streams (two Windows Explorer > file > copy operations on the same workstation) will max the wire at 92Mb/s, or > 11MB/s. > > Our symptoms are similar, though we may be fighting different causes, given > you > can't even get over 4MB/s. I've provided multiple packet captures as > instructed, but haven't heard anything back yet. That was over a week ago... > > -- > Stan > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Client link utilization
Bostjan Skufca put forth on 2/6/2010 6:14 PM: > Hello everybody! > > This is probably going to be a classic question but I cannot find a > decent answer on net. > > I have samba server set up and the following things work flawlessly: > - iperf shows 92% link utilization > - FTP/SCP/HTTP transfers work in 10MB/s range. > > However, when I mount samba share with linux client (mount.cifs) the > link utilization cannot bypass cca 33%. Transfer speeds constantly > stops around 3.8MB/s and will not rise above it no matter what socket > and locking options I use. > > Do you have any ideas about why this is happening and/or FAQ websites > to point me to? I've had a similar thread running for a few weeks without resolution. In my case I can max the wire (100FDX) at 92Mb/s to/from Win2K and WinXP clients using FTP, and smbclient from the server to shares on the workstations maxes the wire (at least GET from the workstations does). I'm running Samba 3.2.5 on Debian Lenny with custom kernel 2.6.31.1. The max smb performance I can get in a single stream to/from smbd is 65Mb/s, or 8.5MB/s. I've now tested Win2K, WinXP, and smbclient on SLED 10 (can't recall version). In all cases, no matter what performance settings I tweak in smb.conf or on the workstations, I can't get wire speed with a single SMB stream---can't get over 65Mb/s. Interestingly, two simultaneous SMB transfer streams (two Windows Explorer file copy operations on the same workstation) will max the wire at 92Mb/s, or 11MB/s. Our symptoms are similar, though we may be fighting different causes, given you can't even get over 4MB/s. I've provided multiple packet captures as instructed, but haven't heard anything back yet. That was over a week ago... -- Stan -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
