You are not logged in.

#1 2018-01-14 10:38:58

9colai
Member
Registered: 2018-01-14
Posts: 1

Odd network performance to Synology NAS

Hi

I've been trying to get my Samba write performance better without any luck. The performance is worst when i upload files to the server with a file manager like Nemo or Nautilus, there I get 3 MB/s. But when i use cp in terminal i get 13 MB/s and when i use dd to test performance i get close to 20 MB/s at 512MB block size (50 MB/s in read).

The NAS i use is a Synology ds214Play and the CPU/RAM usage is not even near 50% usage, it's the network (Wifi) which is the bottlenet in my hardware setup. In windows the speed is around 25MB/S up and 25 MB/s down.

To compare different protocols, I've created a script that tests the performance by dd with different blocksizes. This is the output for CIFS, NFS and FTP respectively:

CIFS performance

block size 512M - Write
1+0 records in
1+0 records out
536870912 bytes (537 MB, 512 MiB) copied, 31.1246 s, 17.2 MB/s
 
block size 512M - Read
1048576+0 records in
1048576+0 records out
536870912 bytes (537 MB, 512 MiB) copied, 11.6208 s, 46.2 MB/s
 
 ############################################## 
 
block size 64k - Write
8000+0 records in
8000+0 records out
524288000 bytes (524 MB, 500 MiB) copied, 33.1639 s, 15.8 MB/s
 
block size 64k - Read
1024000+0 records in
1024000+0 records out
524288000 bytes (524 MB, 500 MiB) copied, 11.0767 s, 47.3 MB/s
 
 ############################################## 
 
block size 8k - Write
64000+0 records in
64000+0 records out
524288000 bytes (524 MB, 500 MiB) copied, 106.29 s, 4.9 MB/s
 
block size 8k - Read
1024000+0 records in
1024000+0 records out
524288000 bytes (524 MB, 500 MiB) copied, 10.863 s, 48.3 MB/s
NFS performance

block size 512M - Write
1+0 records in
1+0 records out
536870912 bytes (537 MB, 512 MiB) copied, 28.2652 s, 19.0 MB/s
 
block size 512M - Read
1048576+0 records in
1048576+0 records out
536870912 bytes (537 MB, 512 MiB) copied, 13.2983 s, 40.4 MB/s
 
 ############################################## 
 
block size 64k - Write
8000+0 records in
8000+0 records out
524288000 bytes (524 MB, 500 MiB) copied, 32.8344 s, 16.0 MB/s
 
block size 64k - Read
1024000+0 records in
1024000+0 records out
524288000 bytes (524 MB, 500 MiB) copied, 12.9972 s, 40.3 MB/s
 
 ############################################## 
 
block size 8k - Write
64000+0 records in
64000+0 records out
524288000 bytes (524 MB, 500 MiB) copied, 107.09 s, 4.9 MB/s
 
block size 8k - Read
1024000+0 records in
1024000+0 records out
524288000 bytes (524 MB, 500 MiB) copied, 12.7637 s, 41.1 MB/s
 
FTP performance

block size 512M - Write
1+0 records in
1+0 records out
536870912 bytes (537 MB, 512 MiB) copied, 29.7416 s, 18.1 MB/s
 
block size 512M - Read
1048576+0 records in
1048576+0 records out
536870912 bytes (537 MB, 512 MiB) copied, 14.4373 s, 37.2 MB/s
 
 ############################################## 
 
block size 64k - Write
8000+0 records in
8000+0 records out
524288000 bytes (524 MB, 500 MiB) copied, 30.4627 s, 17.2 MB/s
 
block size 64k - Read
1024000+0 records in
1024000+0 records out
524288000 bytes (524 MB, 500 MiB) copied, 15.2931 s, 34.3 MB/s
 
 ############################################## 
 
block size 8k - Write
64000+0 records in
64000+0 records out
524288000 bytes (524 MB, 500 MiB) copied, 30.5498 s, 17.2 MB/s
 
block size 8k - Read
1024000+0 records in
1024000+0 records out
524288000 bytes (524 MB, 500 MiB) copied, 18.9607 s, 27.7 MB/s

I've tried to tweak different settings without any luck. I have tried following guides from the following sites:
https://wiki.archlinux.org/index.php/Sa … erformance
https://wiki.archlinux.org/index.php/Sy … erformance

I tried setting CIFSMaxBufSize=130048 in modprobe.d (Don't even know if it affects Arch)
I tried wsize=130048 as option when mounting

Non of the above had any effect on the performance.

This is my smb.conf file:

[global]

# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
   workgroup = WORKGROUP

# server string is the equivalent of the NT Description field
   server string = Samba Server

# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller".
#
# Most people will want "standalone server" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
   server role = standalone server

# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
;   hosts allow = 192.168.1. 192.168.2. 127.

# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
;  guest account = pcguest

# this tells Samba to use a separate log file for each machine
# that connects
   log file = /usr/local/samba/var/log.%m

# Put a capping on the size of the log files (in Kb).
   max log size = 50

# Specifies the Kerberos or Active Directory realm the host is part of
;   realm = MY_REALM

# Backend to store user information in. New installations should 
# use either tdbsam or ldapsam. smbpasswd is available for backwards 
# compatibility. tdbsam requires no further configuration.
;   passdb backend = tdbsam

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting.
# Note: Consider carefully the location in the configuration file of
#       this line.  The included file is read at that point.
;   include = /usr/local/samba/lib/smb.conf.%m

# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
;   interfaces = 192.168.12.2/24 192.168.13.2/24 

# Where to store roving profiles (only for Win95 and WinNT)
#        %L substitutes for this servers netbios name, %U is username
#        You must uncomment the [Profiles] share below
;   logon path = \\%L\Profiles\%U

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
;   wins support = yes

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
#	Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;   wins server = w.x.y.z

# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one	WINS Server on the network. The default is NO.
;   wins proxy = yes

# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The default is NO.
   dns proxy = no 

# These scripts are used on a domain controller or stand-alone 
# machine to add or delete corresponding unix accounts
;  add user script = /usr/sbin/useradd %u
;  add group script = /usr/sbin/groupadd %g
;  add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
;  delete user script = /usr/sbin/userdel %u
;  delete user from group script = /usr/sbin/deluser %u %g
;  delete group script = /usr/sbin/groupdel %g

  usershare path = /var/lib/samba/usershare
  usershare max shares = 100
  usershare allow guests = yes
  usershare owner only = yes
  
  server min protocol = SMB2
  client signing = disabled



#============================ Share Definitions ==============================
[homes]
   comment = Home Directories
   browseable = no
   writable = yes

# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
;   comment = Network Logon Service
;   path = /usr/local/samba/lib/netlogon
;   guest ok = yes
;   writable = no
;   share modes = no


# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
;    path = /usr/local/samba/profiles
;    browseable = no
;    guest ok = yes


# NOTE: If you have a BSD-style print system there is no need to 
# specifically define each individual printer
[printers]
   comment = All Printers
   path = /usr/spool/samba
   browseable = no
# Set public = yes to allow user 'guest account' to print
   guest ok = no
   writable = no
   printable = yes

# This one is useful for people to share files
;[tmp]
;   comment = Temporary file space
;   path = /tmp
;   read only = no
;   public = yes

# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
;   comment = Public Stuff
;   path = /home/samba
;   public = yes
;   writable = no
;   printable = no
;   write list = @staff

# Other examples. 
#
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
;   comment = Fred's Printer
;   valid users = fred
;   path = /homes/fred
;   printer = freds_printer
;   public = no
;   writable = no
;   printable = yes

# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
;   comment = Fred's Service
;   path = /usr/somewhere/private
;   valid users = fred
;   public = no
;   writable = yes
;   printable = no

# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %U option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
;  comment = PC Directories
;  path = /usr/pc/%m
;  public = no
;  writable = yes

# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
;[public]
;   path = /usr/somewhere/else/public
;   public = yes
;   only guest = yes
;   writable = yes
;   printable = no

# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
;   comment = Mary's and Fred's stuff
;   path = /usr/somewhere/shared
;   valid users = mary fred
;   public = no
;   writable = yes
;   printable = no
;   create mask = 0765

Can anybody tell me what I can do?

Best regards
Nicolai

Offline

#2 2018-01-17 06:51:57

Docbroke
Member
From: India
Registered: 2015-06-13
Posts: 1,433

Re: Odd network performance to Synology NAS

9colai wrote:

it's the network (Wifi) which is the bottlenet in my hardware setup

May be the issue is with wifi driver on your computer.

Have you tried sshfs for comparison with cifs,nfs etc.

Offline

Board footer

Powered by FluxBB