ReadyNAS 104 - Super Slow Performance (25K/s) #24257207

[stydie]

Hi all,

I'm a loyal ReadyNAS user... I have a ReadyNAS Ultra v2 (awesome) and a ReadyNAS 104 (crappy). I am astonished that I can't stream video straight off the 104 through Plex (that's another complaint).

Anyway, I have a Netgear R6200 gigabit / 802.11ac router that has both the NAS units plugged into it. They show as gigabit connection speed when I look at the "status" in the web interface.

I have a desktop and two laptops connected to the router via wireless (all 802.11ac). Any time I do any transfer between ANY device (laptop, desktop, the UltraNAS) and the 104, the speed is slowwwww (25K/s). I ran the NAS speed test on it... got 25K/s.

I also tried the MTU test to ping the 104 with 1472 and got a fine TTL (65ms).

the Ultra v2 works GREAT with good throughput. The 104, not so much.

I'm sure there's some weird configuration issue with the 104 or my router, but I can't figure it out. Would LOVE if anyone could help me resolve this.

Thanks!
-Chris

[StephenB]

What speed do you see if you connect one of the PCs to the R6200 with gigabit ethernet?

[TonV]

Are you using ReadyNas Remote? I believe this installs a LEAF network adapter and I've had that ruin the performance on my RN104 before... You could try to remove it...

Sent from my SM-P900 using Tapatalk

[mdgm-ntgr]

If you like send me your logs (see the link in my sig)

[stydie]

Well I can't believe I'm such a bonehead... I plugged my laptop directly into the router and was able to copy 200MB files back and forth in about a second or two.

I'm still wondering why the speed over wireless is so incredibly slow... when I can download from the internet (through my wireless router) at 700Kb-1MB a second.

Any ideas why the NAS would be so fast over wired but crippled over wireless?

And mdgm - I'll try to pull the logs tonight.

[mdgm-ntgr]

What version of Windows are you running on your PC?

Perhaps try lowering the MTU on your PC a bit more to e.g. 1430?

[StephenB]

I'd find the MTU rather than just change settings blindly. Open CMD and enter

ping -f -l XXXX NASIPADDRESS

where xxxx is a number <= 1472.

If 1472 works as usual, then the MTU is 1500 (XXXX+28).
If you get a "Packet needs to be fragmented but DF set." then lower XXXX until you find the largest that works.

Add 28 to that largest XXXX, and you have the MTU.

[stydie]

I'm running Windows 7 64 bit.

I tried pinging at 1472 and 1430 - worked fine. Still experiencing extremely low transfer speed over wireless.

C:\Users\stydie>ping -f -l 1472 192.168.1.3

Pinging 192.168.1.3 with 1472 bytes of data:
Reply from 192.168.1.3: bytes=1472 time=44ms TTL=64
Reply from 192.168.1.3: bytes=1472 time=112ms TTL=64
Reply from 192.168.1.3: bytes=1472 time=47ms TTL=64
Reply from 192.168.1.3: bytes=1472 time=7ms TTL=64

Ping statistics for 192.168.1.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 112ms, Average = 52ms

C:\Users\stydie>ping -f -l 1472 192.168.1.2

Pinging 192.168.1.2 with 1472 bytes of data:
Reply from 192.168.1.2: bytes=1472 time=25ms TTL=64
Reply from 192.168.1.2: bytes=1472 time=22ms TTL=64
Reply from 192.168.1.2: bytes=1472 time=5ms TTL=64
Reply from 192.168.1.2: bytes=1472 time=5ms TTL=64

Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 25ms, Average = 14ms

C:\Users\stydie>ping -f -l 1430 192.168.1.2

Pinging 192.168.1.2 with 1430 bytes of data:
Reply from 192.168.1.2: bytes=1430 time=14ms TTL=64
Reply from 192.168.1.2: bytes=1430 time=3ms TTL=64
Reply from 192.168.1.2: bytes=1430 time=8ms TTL=64
Reply from 192.168.1.2: bytes=1430 time=8ms TTL=64

Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 14ms, Average = 8ms

C:\Users\stydie>ping -f -l 1430 192.168.1.3

Pinging 192.168.1.3 with 1430 bytes of data:
Reply from 192.168.1.3: bytes=1430 time=1ms TTL=64
Reply from 192.168.1.3: bytes=1430 time=9ms TTL=64
Reply from 192.168.1.3: bytes=1430 time=8ms TTL=64
Reply from 192.168.1.3: bytes=1430 time=3ms TTL=64

Ping statistics for 192.168.1.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 9ms, Average = 5ms

C:\Users\stydie>

[mdgm-ntgr]

You're getting much better times when using the lower MTU of 1430.

Can you try lowering the MTU on your wireless NIC and then seeing if your speeds improve. If it doesn't help you can change this setting back.

[stydie]

Ah, ok. So I'm a bit confused where to change these settings. I have router settings, I have settings on my desktop and laptop NIC, I have the setting on the NAS... which ones do I change?

I'm also really confused as to how I change the MTU on each of my computers...

I noticed on the v2Duo the setting is right on the settings page but on the 104 I don't see anywhere to change these advanced settings.

Also, should I enable jumbo frames and such?

[StephenB]

Certainly don't enable jumbo frames if you are reducing the MTU below the normal 1500. Jumbo Frames are packets that are larger than 1500 (usually 4000 to 9000).

On the RN104, click on "network", then on the settings wheel over the adapter.
On a PC you generally need to do this from the command line.
Normally you wouldn't touch the router settings, but need to make sure that all your devices are below the router threshold.

Honestly, the default 1500 MTU should simply work. My R6300v2 (and my 7000) both work perfectly with the default ethernet MTU of 1500, and your R6200 should as well.

What wifi card is in your PC?

[stydie]

Yeah, I don't know why it's not working. Do I need to drop the MTU to 1458 on all devices or just on my PC and laptop?

I did this and I got the ReadyNAS Ultra 4 Plus up to about 3MB/s transfer (still crappy). Tested the 104 and it came to around 5MB/s. Improvement...

I have a TP-LINK 450Mbps Wireless N Adapter.

[mdgm-ntgr]

Try on just your PC or laptop for a start and see if it helps.

[stydie]

See above, mdgm. I changed all MTUs to 1458. Also emailed you my logs.

Also, I'm trying to stream 1080P video straight over the wireless from the 104 and it's lagging HARD.

Netgear Genie is also showing that there are 3 other networks on channel 11. Don't know if I should switch channels?

[mdgm-ntgr]

What about with a lower MTU still of 1430?

[stydie]

Same result with 1430 settings all around. 3MB/s throughput from both NAS's.

[mdgm-ntgr]

I don't think this problem has got anything to do with the MTU, now that I have had another look at it, and considering that your Ultra works fine.

I saw this in your initrd.log

[2014/02/04 10:01:12] Updated from ReadyNASOS 6.0.0 to 6.1.5.
[2014/02/20 01:38:12] Updated from ReadyNASOS 6.1.5 to 6.1.6.
[2014/11/19 19:13:06] Updated from ReadyNASOS 6.1.6 (1391111179) to 6.1.9 (1409791183).
[2014/11/25 22:39:23] Updated from ReadyNASOS 6.1.9 () to 6.2.0 (ReadyNASOS).

You last did a factory reset on the very first ReadyNAS OS firmware.

I would suggest that you backup your data, do a factory default (wipes all data, settings, everything) then restore your data from backup. I would have suggested when you got the unit to have done a factory after upgrading to the latest firmware. We made a change in 6.1.5 to use a larger nodesize/leafsize when creating a new volume, which should help.

Also, I would not use snapshots on every share, just on ones you really need it for on the 104.

I would suggest you change your MTU back to the default (either before backing up your data or after), whichever you prefer.

Also your Ultra is very full. I would not recommend leaving your volume as full as it is. Leaving your volume practically 100% full will lead to poor write performance.

[stydie]

Hm, darn... a backup of 8TB worth of data is going to be pretty brutal. Wish there was another way.

How do I disable snapshots on my shares?

[mdgm-ntgr]

Go to Shares in the Dashboard, select the share, go to the settings and disable snapshots/protection. You can delete some snapshots from the timeline view.

I thought it was your Ultra that had 8TB on it? On that one you should free up some space, but you don't have to.

[Retired_Member]

I made similar experience this week. While data transfer from Mac OS to the ReadyNAS 104 performed ok, my Windows Vista experienced very bad network throughput.
I cancelled my Windows backup after about 10h. At this time it had about 200GB of data transferred from Vista to the NAS (about 5-6MB/sec). Looking into the Windows task manager my network utilization was max. about 50% (Windows 100Mbit, Eth Switch + NAS both using Gbit).
After searching around I found some great advice on speedguide.net (articles / windows-7-vista-2008-tweaks-2574).
After following the referenced article the Windows task manager now shows network utilization of 99% to 100%.
My data transfer from Windows to NAS is currently running with more than 11MB/sec which is what I expect for 100Mbit network.

Before tuning ...
(netsh int tcp show global)

Receive-Side Scaling State: enabled
Chimney Offload State: disabled
Receive Window Auto-Tuning Level: highlyrestricted
Add-On congestion Control Provider: none
ECN Capability: disabled
RFC 1323 Timestamps: disabled

plus message
** The above autotuninglevel setting is the result of Windows Scaling heuristics overriding any local/policy configuration on at least one profile.

After tuning (ensure to run tuning cmds with admin authority) ...

Receive-Side Scaling State: enabled
Chimney Offload State: enabled
Receive Window Auto-Tuning Level: normal
Add-On congestion Control Provider: ctcp
ECN Capability: disabled
RFC 1323 Timestamps: disabled

CPU and Memory are looking same than before the network tuning.
I did not change the default MTU size of 1500.

Don't know if this applies to your performance issue, too, but I think it's worth to check this.
Regards,
Holger