Jump to content

squirrelslikenuts

Members
  • Posts

    46
  • Joined

  • Last visited

Report Comments posted by squirrelslikenuts

  1. 1 hour ago, gubbgnutten said:

    For completeness - How fast are writes to the parity protected array (for a share not using cache)?

     

     

    When you do the write tests, what are you writing? (number of files, total size of data).

     

    I would expect all writes over the network to occur at line speed until the RAM buffer on the server is full, and you do have plenty of RAM.

     

    Test Disk 6 (wd red 4tb) - disabled cache - using parity

     

    Absolutely steady at 102 MB/s WRITE  for ~25 GB - MKV files

     

    Steady at 102 MB/s WRITE for 25/100GB vdmk file (vmware disk image)

    Around 25GB mark, the wirte slows to ~59 MB/s

     

    I will say that I have about ~20ish mbit of bandwidth on the network being used by ip cameras but they are pushing data to a different physical server on the network. Im not expecting 125 MB/s read and write  but I would like to see 100 MB/s both ways.

     

    Cache drive is a 960GB NVMe - I doubt Id push more than that to the array at any given time.

     

    EVERYONE on the net says "wahhh wahhh my writes are slow" I seem to be the only one able to achieve 100 MB/s out of the box but complain my reads are slow. 

     

     

    My network is as follows

     

    Internet -> pfSense box -> GbE switch -> many computers including the server

    Static IPs set to all devices

     

     

     

     

  2. 1 hour ago, johnnie.black said:

    A few things to try:

     

    - see if there's any difference reading from a disk share vs an user share

    - toggle Direct IO (Settings -> Global Share settings)

    - some time ago using an older SMB version could make a big difference, not so much recently but worth a try, for example to limit to SMB 2, add to "Samba extra configuration" on Settings -> SMB:

    
    max protocol = SMB2_02

     

    NO CACHE - Disk 6 Share - Empty drive - USES PARITY (not user share)

    Write from Win7 -> unRAID - 48GB MKV

    102MB/s tapering to ~50-60 MB/s around the 23GB mark

    72 MB/s Average Speed

    Average CPU Load is 8-9%

     

    iotop reveals 4 lines of code below @ ~25 MB/s each (while running at full speed)

    shfs /mnt/user -disks 127 2048000000 -o noatime,big_writes,allow_other -o direct_io -o remember=0

    Direct I/O is/was enabled 

     

    Read Speed starts out around 3.5 MB/s ( I didnt catch what it maxed at)

    20GB MKV - 46 MB/s average read (saving to ssd on windows machine)

     

     

    120GB SSD (unassigned)

    Write speeds to an unassigned 120GB ssd on the unRAID system (outside array and not cached)

    48 GB MKV

    Steady at ~103 MB/s write - Spiked down to ~65 MB/s within the last 2% of the copy

    Average 100 MB/s for the fill 48 GB

     

    Read Speed started off at a 500 KB/s then ramped to 65 MB/s and stayed there until complete

    Average 61 MB/s

     

     

    I will try the max protocol SMB setting you suggested next. If that fails I will reduce the network clutter down to just the unraid box and client machine connected to the switch. I can't see that helping as iperf speed tests, and write speeds look flawless.

     

  3. 1 minute ago, limetech said:

    That's about what you would expect right?

     

    I'm thinking there might be two changes affecting this:

    1. Do you have 'Enhanced OS X interoperability' set to Yes?  If so, set to No and see if transfer rate increases.
    2. We changed TCP congestion control to BBR for Unraid 6.7.  You can change it back previous 'reno' default by typing this command:
      
      echo reno > /proc/sys/net/ipv4/tcp_congestion_control

      Then see if transfer rate increases.

    100 MB/s is what I'd expect for read speeds. The drives are capable of more than 100 MB/s read. And I can write at faster than 100 MB/s over the network, so I know the hardware can handle it.

     

    Will try your suggestions and report back.

     

    Im 5 days into my 15 day trial extension and basically this is the last issue to fix before purchasing the license.

     

     

×
×
  • Create New...