LAN speed
-
@DustinB3403 said:
@Dashrender It's never a best practice, but to pinpoint causes of trouble sometimes you must.
We've eliminated that as a possible concern already.
-
Okay, moving on from the NIC which is a red herring, let's talk about where the issues CAN be....
They could be...
- That the NAS cannot go faster than this. NICs do not determine the speed that can be achieved, the device does. What is the setup of the device, the protocols, the actions that are being measured at 5.5MB/s (aka 44Mb/s.)
- The network is saturated causing it to slow down to this speed. The NIC we know for certain is much faster than the speed that you are getting in the transfer. So if the network is the issue, it is from a bottleneck along the path. This is extremely unlikely as LAN bottlenecks in the switched networking world for SMBs pretty much don't exist until you start adding VLANs and getting silly.
- The device receiving the files cannot receive them any faster than this. The bottleneck can be either end.
-
ok, i think i will keep it as it is "auto"
-
So we need to figure out if the speed issue exists from the sending point, the receiving point or along the path.
-
You would not expect to be getting 1Gb/s in any way from even a perfect NAS able to stream from memory. With Ethernet, TCP/IP and iSCSI overhead alone you'd normally max out around 800Mb/s and with NFS or SMB a little lower than that. That's if perfect.
Typically storage is measured in IOPS, not in through (bandwidth) because this is what matters nearly all of the time. Throughput does matter, but isn't what generally impacts us. You almost never see storage requirements written in anything but IOPS. This is because of how storage happens... the delays and performance issues almost always come from an inability to "do different things" rather than to stream data on or off. If you plan to use this as a streaming media server, that could be different, but for normal use, throughput isn't a real concern.
-
In order to measure throughput in any real way you need a single, extremely large file that will transfer for twenty minutes or so and a receiving unit that has "unlimited" ability to accept the file (preferably into memory, not disk) and a network that you know has no saturation (this could be a quiet switch, a switch with nothing but this connection or a crossover cable.) Eliminate the "noise" and things that cause interruptions so that you can, as clearly as possible, look only at the throughput.
-
Scott - what tool would you use to create a 120 GB file to keep a 1 Gb link saturated for 20 mins (assuming 800 Mb/s transfer)?
-
@scottalanmiller said:
@IT-ADMIN said:
@DustinB3403 said:
Can you go into the network page on the NAS, and screen shot that for us?
I have a feeling the speed within the NAS is set to Auto. Which if it is, is likely causing the performance of the NIC to be slow. So either there is something wrong with the configuration on your Switch. Or the NAS.
yes you are right, the link speed is set to auto, should i change it to 1000 ??
No, it is working perfectly now. GigE requires Auto. Setting it to 1000 is an unofficial mode only supported by a few vendors who don't follow the specs.
Now that you say that - I do recall something about Auto being the standard - Is that in an RFC?
-
now the speed is 24.2 MB/s
-
Well you're at 201 Mb/s now - what protocol are you using? SMB 2.0/3.0?
-
-
maybe if i change it to SMB 3.0 i will get more speed
-
???
-
@Dashrender said:
Scott - what tool would you use to create a 120 GB file to keep a 1 Gb link saturated for 20 mins (assuming 800 Mb/s transfer)?
dd will do that, if you are on the NAS CLI.
-
@Dashrender said:
@scottalanmiller said:
@IT-ADMIN said:
@DustinB3403 said:
Can you go into the network page on the NAS, and screen shot that for us?
I have a feeling the speed within the NAS is set to Auto. Which if it is, is likely causing the performance of the NIC to be slow. So either there is something wrong with the configuration on your Switch. Or the NAS.
yes you are right, the link speed is set to auto, should i change it to 1000 ??
No, it is working perfectly now. GigE requires Auto. Setting it to 1000 is an unofficial mode only supported by a few vendors who don't follow the specs.
Now that you say that - I do recall something about Auto being the standard - Is that in an RFC?
Yes. The GigE RFC states that only Auto can be used. Cisco uses their own standard that isn't true Ethernet. One of the many reasons I avoid craptastic Cisco gear. Non-standard Ethernet? You've got to be kidding me.
-
@IT-ADMIN said:
now the speed is 24.2 MB/s
Awesome. It was probably just small files being used and not getting a chance for the TCP/IP tuning to kick in yet. That shows that you are getting the GigE connection for sure.
-
@IT-ADMIN said:
@Dashrender said:
Well you're at 201 Mb/s now - what protocol are you using? SMB 2.0/3.0?
SMB 2.0
SMB is not very efficient. Not like it cuts your throughput by 75% or anything, but you don't use SMB for speed. NFS is quite a bit faster. But this should not be an issue. Sounds like you are getting fine performance.
-
@IT-ADMIN said:
maybe if i change it to SMB 3.0 i will get more speed
Likely less. SMB 3 does more, not less.
-
@IT-ADMIN said:
now the speed is 24.2 MB/s
Notice here that you are copying 79K items, not a single item. So you are not getting anywhere near the potential throughput unless individual items are many GB in size, then you could only look during those specific items. If that PST is 10GB, for example, you should see it get much, much faster than if you have tons of 4KB files. Each file requires the SMB protocol to set up and tear down the connection. It is not efficient for this kind of access at all.
-
@scottalanmiller said:
@Dashrender said:
Scott - what tool would you use to create a 120 GB file to keep a 1 Gb link saturated for 20 mins (assuming 800 Mb/s transfer)?
dd will do that, if you are on the NAS CLI.
dd in=/dev/zero of=zero.txt bs=4k count=400000
Pay attention to the output when it finished. It will also give you some information on how fast it wrote zeros to the drives. You can then use zero.txt to transfer to different points on the network.
Don't forget to delete that file when you're finished, it's literally 1GB of zeros.
