Network Speed
#21
(10-23-2017, 07:22 AM)stuartiannaylor Wrote:
(10-23-2017, 05:53 AM)Luke Wrote:
(10-23-2017, 04:59 AM)rontant Wrote: There seems to be nothing wrong with your USB 3 drive. I think you have a valid point to suspect client side. Anyway, here is my SMB config file /etc/samba/smb.conf.

Code:
[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
  workgroup = EASTWING

# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
#   wins support = no

# 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

# This will prevent nmbd to search for NetBIOS names through DNS.
  dns proxy = no

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;   interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;   bind interfaces only = yes


#### Debugging/Accounting ####

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

# Cap the size of the individual log files (in KiB).
  max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
#   syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
  syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
  panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# 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 sever" 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

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.  
#   passdb backend = tdbsam

#   obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
#   unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<[email protected]> for
# sending the correct chat script for the passwd program in Debian Sarge).
#   passwd program = /usr/bin/passwd %u
#   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
#   pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
  map to guest = bad user

########## Domains ###########

#
# The following settings only takes effect if 'server role = primary
# classic domain controller', 'server role = backup domain controller'
# or 'domain logons' is set
#

# It specifies the location of the user's
# profile directory from the client point of view) The following
# required a [profiles] share to be setup on the samba server (see
# below)
;   logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
#   logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;   logon drive = H:
#   logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;   logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.  
# The following assumes a "machines" group exists on the system
; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.  
; add group script = /usr/sbin/addgroup --force-badname %g

############ Misc ############

# 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
;   include = /home/samba/etc/smb.conf.%m

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
;   idmap uid = 10000-20000
;   idmap gid = 10000-20000
;   template shell = /bin/bash

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
;   usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
  usershare allow guests = yes

#======================= Share Definitions =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[homes]
;   comment = Home Directories
;   browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
;   read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
;   create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
;   directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# Un-comment the following parameter to make sure that only "username"
# can connect to \\server\username
# This might need tweaking when using external authentication schemes
;   valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
;   comment = Network Logon Service
;   path = /home/samba/netlogon
;   guest ok = yes
;   read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no
;   create mask = 0600
;   directory mask = 0700

#[printers]
#   comment = All Printers
#   browseable = no
#   path = /var/spool/samba
#   printable = yes
#   guest ok = no
#   read only = yes
#   create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
#[print$]
#   comment = Printer Drivers
#   path = /var/lib/samba/printers
#   browseable = yes
#   read only = yes
#   guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin

[public]
  comment = I have no comment
  path = /public
  public = yes
  browseable = yes
  only guest = yes
  writable = yes
;   printable = no
  create mask = 0777

[public2]
  comment = I have no comment
  path = /public2
  public = yes
  browseable = yes
  only guest = yes
  writable = yes
  create mask = 0777

[public3]
  comment = I have no comment
  path = /public3
  public = yes
  browseable = no
  only guest = yes
  writable = yes
  create mask = 0777

Ok, just checked - the issue is not with the R64 OMVserver, instead there is something wrong with SMB client on my Linux Mint 18.2 desktop PC. On Win10 I'm getting normal transfer speeds. 

Which leads me to this question: @stuartiannaylor what OS are you running on your desktop PC ?

Strangely Win10 for SMB accessing a share on the Rock64 but just a straight samba setup on Ayufan 16.04 minimal if I remember rightly.
I will run through all the tests again this week sometime.

Try the OMV image and see what speeds you get.
You can find me on IRC, Discord and Twitter


  Reply
#22
I am using Ayufan Artful Minimal. I have tried Ayufan Jessie Minimal and Stretch as well. No issue with Samba.
  Reply
#23
(10-23-2017, 07:07 PM)rontant Wrote: I am using Ayufan Artful Minimal.  I have tried Ayufan Jessie Minimal and Stretch as well. No issue with Samba.

Ayufan Xenial Arm64 minimal seems to suck for me.

Just tried the DietPi image from Win10 SSD to Ramdisk Rock64 Share and got near Theoretical max on 1Gbs (114MBs).

Impressed with the DietPi image for quick setup of a whole range of software and services.

820Mb took approx 8 secs to copy.
  Reply
#24
Hijacking the thread Big Grin

I'm on stretch-mate-rock64-0.5.15-136-20171222-arm64 default "ondemand" CPU governor
1gb link MikroTik routerboard + D-Link 1gb switch.
2x Win 10 1gb link on the other side.

Initially my Rock64 managed to work 114MB/s up and 114MB/s down by using eMMC NAND with Samba.
It was 114MB/s up and 63MB/s down over USB HDD.

Something happened, I don't know why, but now it's max 63MB/s up and spikes between 30MB/s and 90MB/s down via NAND. Yes, actually NAND write/download speed is way better than read/upload speed.
USB gone spiking 50MB/s ~ 63MB/s read/upload and 13MB/s ~18MB/s write/download.

During spikes system is like freezing for a second.
I'm suspecting overheating. I've got standard Rock64 recommended radiator and SoC temp 35 ~ 40 when iddle and 52 ~60 degrees when copying over SMB. It happens on 2 different Win 10 1GB LAN speed.
Copying between laptops via SMB share is stable 114MB/s.

I'm going to buy aluminium 2x 20x20x10 heatsink for CPU and GPU + 1x 14z14x6 heatsink for eMMC + 3M thermal adhesive tape and will check any improvement.

I have tried reflashing clean system already.

Any ideas beside heating problem?
Should I try different Linux distribution?

Main purpose of my Rock64 is SMB media server for 4K streaming so fast SMB is priority.

Checked NFS already, and for Windows 10, NFS speed is slower way slower than SMB.
  Reply
#25
You're not the only one. Someone can transfer via samba at speeds above 80MB/s, others have performance similar to yours.

This is the result of my last test.
https://forum.pine64.org/showthread.php?...1#pid35291

I too noticed lower performance via NFS.
  Reply
#26
Weird thing is, it worked just all fine the first day.
Debian arm64 - worked fine.
Ubuntu - speed dropped (because of armhf?)
Back to Debian arm64 - worked fine.
Played with Debian for couple days and spotted speed dropped.

Tried unplugging all cables except for power and LAN.
Reflashed clean system.
If it was USB only, I'd blame slow HDD but it happens on NAND also.
I just hope it's overheating problem and bigger heat sink will help. *fingers crossed*
  Reply
#27
Hey guys! I'm trying to troubleshoot why my speed on OMV is so unbearably slow

I'm doing 1-3mbps over wifi, and I can't begin to think why it's so slow, especially after seeing so many messages with the slowest speed being at least 14mbps

My setup- 
Rock64 1GB with jessie-openmediavault-rock64-0.5.15-136-armhf.img installed on an SD card
I have an external USB 3.0 HDD plugged into a powered USB 3.0 hub
I've configured SMB/CIFS, and can't do NFS because of my operating system (Windows 8.1)

If I can get speeds even close what you all have (I'd honestly even be happy with 30mbps at this point), that'd make my day

Thanks for the help!
  Reply
#28
(05-04-2018, 10:34 PM)CrouchingDragon Wrote: Hey guys! I'm trying to troubleshoot why my speed on OMV is so unbearably slow

I'm doing 1-3mbps over wifi, and I can't begin to think why it's so slow, especially after seeing so many messages with the slowest speed being at least 14mbps

My setup- 
Rock64 1GB with jessie-openmediavault-rock64-0.5.15-136-armhf.img installed on an SD card
I have an external USB 3.0 HDD plugged into a powered USB 3.0 hub
I've configured SMB/CIFS, and can't do NFS because of my operating system (Windows 8.1)

If I can get speeds even close what you all have (I'd honestly even be happy with 30mbps at this point), that'd make my day

Thanks for the help!

Wooow man, you are touching very fragile point in here.
Wi-Fi has numerous conditions to work on acceptable level even on professional equipment.

First of all quality of your router, cards, device/antena position, power consumption, drivers, neighbours etc.
Couple practical advises from router perspective / N standard usage:
- put your router as high as possible
- find free/less crowded chanel (you can use some software on your phone) - feel free to test every chanel from 1 to 13 - whatever gives you good connection.
- enable 40mhz wide bandwidth (you are literally enabling 2nd chanel so if your client supports it, you are enabling twice faster connection) and make sure your client has it also enabled as well as any power saving features disabled (decreased speed for less power consumption)
- Do not ever use TKIP or TKIP+AES encryption (use AES only) for password as TKIP messes N-standard speed.

Post your hardware (router, clients, how they are connected etc.).
  Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  low speed wifi pas059 4 252 05-13-2019, 12:09 PM
Last Post: pas059
Bug Fan speed controlled by CPU temp script mikedhoore 2 987 01-14-2019, 05:16 PM
Last Post: va88

Forum Jump:


Users browsing this thread: 1 Guest(s)