samba - May 2018 - Speedup windows client [was] What is the maximum speed for download from a samba share

As counter example. 
My slowest server, AMD E350 2 core, max 1.6Gz. 
On 1Gb lan, disk 2x 5400rpm software raid 1 + 1 ssd. 

Copy Speed 115Mb/s as in max 1Gb bandwith, from a win7 and win10 pc to the
raid1.

File sizes. 
100Mb+ get max 115Mb/s 		to a 4MB blocksized partition.
1-10mb files ,max 90-115Mb/s 	 to a 1MB blocksized partition.
0.0-1mb files  ,max 60-100Mb/s to a 4k blocksized partition.

I get these speeds while im watching my kodi. ;-)  Samba 4.6.x on ubuntu 17.10 
One note here, i use kernel 4.16.1 from
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D
Thats mostly for kodi and the amd GPU driver, but i do notice bit better
perfomance with these higher kernels.

Is the Lenovo Thinkpad T520 with Windows 7, connecting over Wifi? 
Because on wifi, even if i set my laptop 3 meters from the AP, i dont get max.
About 1/2 the speeds, if lucky 3/4 the above speeds. 
Test you wifi with inSSIDer, optimze the chanels. 
Gave me about +25% speed at home on the wifi.
> one of the  virtual machine is the samba VM connected via VPN
> Looking to the cpu usage of this VM ist nearly zero during downloads.
Did you tweak your MTU sizes? 
With things like : 
iptables -A PREROUTING --match policy --pol ipsec --dir in -i eth+ -p tcp -m tcp
--tcp-flags SYN,RST SYN -m tcpmss --mss 1361:1536 -j TCPMSS --set-mss 1360
Maybe disable Path MTU discovery to prevent packet fragmentation problems. Helps
alo  (  net/ipv4/ip_no_pmtu_disc=1  )

Last, login on the proxymod monitor IRQ use, if you have extra cards in the
server, you might have one the using a "shared IRQ"
I make sure, if possible, that my NIC have there own irq set and not a shared
one.

And can you post your smb.conf ? That might help also. 


Greetz, 

Louis

> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens Knut 
> Krüger via samba
> Verzonden: woensdag 25 april 2018 8:29
> Aan: samba at lists.samba.org
> Onderwerp: Re: [Samba] Speedup windows client [was] What is 
> the maximum speed for download from a samba share
> 
> Am 22.04.2018 um 04:30 schrieb L A Walsh via samba:
> > Knut Krüger via samba wrote:
> >>> Limiting the linux-server's max cpu-speed had
> >>> the most affect on performance:
> >>> (limited to 1.6GHz instead of 2.4GHz) (33% limitation)
> >> The server is equipped with an 6 core / 12 tread 3.6 GHz 
> CPU (Intel 
> >> Core i7-980x   and  a Raid 10 Disk array.
> >> The cpu is 90% idle (including webserver traffic and mailserver 
> >> traffic) during downloads.
> > ---
> >    In protocols before cifsV3, only 1 tcp connection was 
> allowed between
> > a user at workstation and a server.  So multi-cores make no
difference.
> Ok this clarifies why two downloads are getting more bandwidth than 1
> >
> >    When you say "the cpu is 90% idle", you realize that
means 10%
> > busy.  10% * 12 cores = 1.2 cores busy.  That may imply one
> > core is "pegged".  Though it sounds unlikely even with a
100Mb
> > network that your cpu is the problem.
> To clarify the setup
> The root server is the 6 core/12 tread machine.
> it is an stretch proxmox installation
> this machine is minimum 90% idle
> 
> one of the  virtual machine is the samba VM connected via VPN
> Looking to the cpu usage of this VM ist nearly zero during downloads.
> There is no difference wehter the VM gets 1 ore more cores or 
> changing 
> the CPU limit.  /CPU Limit us unlimited
> 
> doing some additional test, it seems that a part of the speed lag is 
> client depending.
> 
>     4 core client with Linux is about 25.000 Kbits
>     Lenovo Thinkpad T520 with Windows 7 is the worst client
>     (unfortunately the most important) with 750 kbits/sec  :-(
> 
> So as a first step (as it is really important)  i have to 
> speed up the 
> windows client.
> Any hints?
> 
> After that I will try to speedup the server.
> 
> Kind regards Knut
> >
> >    For my testing, I run my test script on cygwin and
> > "cd" to my home directory on the server (/h) where my
> > test "files" (character devices) are located (/h/zero and
/h/null)
> >
> > From there I usually run it with "bin/iotest".  I'll
attach
> > the bash script.  If you find it of any use, great! else, ignore it.
> > My linux-box has bash-4.4 on it and is currently using a 
> 4.14.0 kernel.
> >
> > Good luck...don't want to overwhelm, so I'll end here.
> >
> >
> >
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
> 
>

Am 25.04.2018 um 09:56 schrieb L.P.H. van Belle via
samba:
> As counter example.
> My slowest server, AMD E350 2 core, max 1.6Gz.
> On 1Gb lan, disk 2x 5400rpm software raid 1 + 1 ssd.
>
> Copy Speed 115Mb/s as in max 1Gb bandwith, from a win7 and win10 pc to the
raid1.
>
> File sizes.
> 100Mb+ get max 115Mb/s 		to a 4MB blocksized partition.
> 1-10mb files ,max 90-115Mb/s 	 to a 1MB blocksized partition.
> 0.0-1mb files  ,max 60-100Mb/s to a 4k blocksized partition.
>
> I get these speeds while im watching my kodi. ;-)  Samba 4.6.x on ubuntu
17.10
> One note here, i use kernel 4.16.1 from
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D
> Thats mostly for kodi and the amd GPU driver, but i do notice bit better
perfomance with these higher kernels.
>
> Is the Lenovo Thinkpad T520 with Windows 7, connecting over Wifi?
> Because on wifi, even if i set my laptop 3 meters from the AP, i dont get
max.
> About 1/2 the speeds, if lucky 3/4 the above speeds.
> Test you wifi with inSSIDer, optimze the chanels.
> Gave me about +25% speed at home on the wifi.
>
>> one of the  virtual machine is the samba VM connected via VPN
>> Looking to the cpu usage of this VM ist nearly zero during downloads.
> Did you tweak your MTU sizes?
No
> With things like :
> iptables -A PREROUTING --match policy --pol ipsec --dir in -i eth+ -p tcp
-m tcp --tcp-flags SYN,RST SYN -m tcpmss --mss 1361:1536 -j TCPMSS --set-mss
1360
> Maybe disable Path MTU discovery to prevent packet fragmentation problems.
Helps alo  (  net/ipv4/ip_no_pmtu_disc=1  )
>
> Last, login on the proxymod monitor IRQ use, if you have extra cards in the
server
it is a virtual machine on a proxmox root server
I just realized that the data transfer rate is going down after a while 
also on a linux workstation to the same slow speed as on windows 
workstation.
the root server is nearly idle
top - 16:46:31 up 313 days,  4:45,  1 user,  load average: 0.25, 0.42, 0.39
Tasks:  39 total,   1 running,  38 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.7 us,  2.9 sy,  0.0 ni, 96.2 id,  0.0 wa,  0.0 hi,  0.1 si,  
0.0 st
KiB Mem:   2097152 total,   767176 used,  1329976 free,        0 buffers
KiB Swap:  2097152 total,    61172 used,  2035980 free,   725864 cached

here the smb.conf

[global]

socket options = TCP_NODELAY SO_RCVBUF=524288 SO_SNDBUF=524288 
SO_KEEPALIVE IPTOS_LOWDELAY

nt acl support = no

   vfs object = recycle
   recycle:repository = Papierkorb
   recycle:keeptree = Yes
   recycle:touch = Yes
   recycle:versions = Yes
   recycle:maxsize = 0
   vfs objects = acl_xattr
   map acl inherit = Yes
   unix charset = ISO-8859-1
   display charset = ISO-8859-1
   security = share
   share modes = yes
   server string = %h server
   dns proxy = no
   interfaces=10.8.2.0/255.255.255.0
   bind interfaces only = yes
   disable netbios = yes
   smb ports = 445
   client NTLMv2 auth = yes
   log file = /var/log/samba/log.%m
   max log size = 1000
   syslog = 0
    panic action = /usr/share/samba/panic-action %d


    encrypt passwords = true
    passdb backend = tdbsam
    obey pam restrictions = yes
    unix password sync = yes
    passwd program = /usr/bin/passwd %u
    passwd chat = *Enter\snew\s*\spassword:* %n\n 
*Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
    pam password change = yes
    map to guest = bad user
    load printers = no
    printing = bsd
    printcap name = /dev/null
    disable spoolss = yes
    usershare allow guests = no

min receivefile size = 2048
use sendfile = true
aio read size = 2048
aio write size = 2048
write cache size = 1024000
read raw = yes
write raw = yes
getwd cache = yes
oplocks = yes
max xmit = 32768
dead time = 15
large readwrite = yes


[homes]
    comment = Home Directories
    browseable = yes
    read only = no
    valid users = %S

[test]
   vfs object = recycle
   recycle:repository = Papierkorb
   recycle:keeptree = Yes
   recycle:touch = Yes
   recycle:versions = Yes
   recycle:maxsize = 0
   path = /var/datas/test/
   public = yes
   writable = yes
   read only = no
   comment = smb share
   printable = no
   guest ok = yes
   create mode = 0775
   force user = root
   force group = root

On Wed, 2 May 2018 16:59:46 +0200
Knut Krüger via samba <samba at lists.samba.org> wrote:


See inline comments:
> 
> here the smb.conf
Does it work ?
Have you tried running 'testparm ?
You said earlier that this is running on Debian Stretch, so it should
be Samba version 4.5.12
> 
> [global]
> 
> socket options = TCP_NODELAY SO_RCVBUF=524288 SO_SNDBUF=524288 
> SO_KEEPALIVE IPTOS_LOWDELAY
> 
> nt acl support = no
> 
>    vfs object = recycle
>    recycle:repository = Papierkorb
>    recycle:keeptree = Yes
>    recycle:touch = Yes
>    recycle:versions = Yes
>    recycle:maxsize = 0
You might as well remove the vfs recycle lines above, they are also in
the share and the line below renders it inoperative, they need to be
on the same line.
>    vfs objects = acl_xattr
>    map acl inherit = Yes
You are missing 'store dos attributes = Yes'
>    unix charset = ISO-8859-1
>    display charset = ISO-8859-1
>    security = share
The above is absolutely wrong 'share' security was removed some time
ago.
>    share modes = yes
Do you mean 'kernel share modes', if so, it is the default.
>    server string = %h server
>    dns proxy = no
>    interfaces=10.8.2.0/255.255.255.0
>    bind interfaces only = yes
>    disable netbios = yes
>    smb ports = 445
>    client NTLMv2 auth = yes
>    log file = /var/log/samba/log.%m
>    max log size = 1000
>    syslog = 0
>     panic action = /usr/share/samba/panic-action %d
>     encrypt passwords = true
>     passdb backend = tdbsam
>     obey pam restrictions = yes
>     unix password sync = yes
>     passwd program = /usr/bin/passwd %u
>     passwd chat = *Enter\snew\s*\spassword:* %n\n 
> *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
>     pam password change = yes
>     map to guest = bad user
>     load printers = no
>     printing = bsd
>     printcap name = /dev/null
>     disable spoolss = yes
>     usershare allow guests = no
> 
> min receivefile size = 2048
> use sendfile = true
> aio read size = 2048
> aio write size = 2048
> write cache size = 1024000
> read raw = yes
> write raw = yes
> getwd cache = yes
> oplocks = yes
> max xmit = 32768
> dead time = 15
I think you mean 'deadtime'
> large readwrite = yes
> 
> 
> [homes]
>     comment = Home Directories
>     browseable = yes
>     read only = no
>     valid users = %S
> 
> [test]
>    vfs object = recycle
>    recycle:repository = Papierkorb
>    recycle:keeptree = Yes
>    recycle:touch = Yes
>    recycle:versions = Yes
>    recycle:maxsize = 0
>    path = /var/datas/test/
>    public = yes
>    writable = yes
>    read only = no
>    comment = smb share
>    printable = no
>    guest ok = yes
>    create mode = 0775
>    force user = root
>    force group = root
How do you think you are running Samba ?
As a Unix domain member or a standalone server ?

Rowland