![]() Socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=131072 SO_SNDBUF=131072 # "testparm" to check that you have not made any basic syntactic # NOTE: Whenever you modify this file you should run the command # behaviour of Samba but the option is considered important # - When commented with "#", the proposed setting is the default # differs from the default Samba behaviour # - When such options are commented with " ", the proposed setting ![]() # Some options that are often worth tuning have been included as Samba has a huge number of configurable options most of which # smb.conf(5) manual page in order to understand the options listed # This is the main Samba configuration file. # Sample configuration file for the Samba suite for Debian GNU/Linux. I had over 1 gig of ram available and CPU usage was just around 5% for all cores (my raspberry pi has 4 cores). I checked the amount of RAM available and CPU usage during copying files through samba - that wasn't a problem. I changed my file according to the first answer of this question. When I ran speed test to the internet (just to check if I'm getting that 100 Mbps on the network), it did gave me values close to 100 Mbps.įrom what I've seen as described above, I can conclude that the problem must be with Samba. I checked the ethernet connection and it is connected with 100 Mbps link. I also ran hdparm and it had a read value also around 80 MiB/sec. I copied a big file from the hard drive back to the hard drive itself and was getting around 80 MiB/sec. I know the problem isn't with the hard drive nor the USB 3.0 SATA connector. The problem is that when I copy files with Samba I only get around 10 MiB/sec. It has a USB 3.0 connection to a hard drive with a Raspberry Pi 4.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |