NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Volume operations causing slowness across SMB
Greetings! I'm trying to understand the behavior that I'm experiencing, whether or not its expected and most importantly, how can I improve it. We are a graphic design shop. We use a lot of Adob...
This is expected. LACP is good for multiple devices.
To determine which Ethernet link to send the packet through, LACP calculates a hash. Here you chose L2+L3. Because you're transferring data from a single client to a single NAS. the source data is always the same, therefore the hash is always the same, therefore the Ethernet link used is always the same. That's why you're capped at the throughput of a single link.
If you want to test the gain in throughput, you need to test from multiple clients simultaneously.
To determine which Ethernet link to send the packet through, LACP calculates a hash. Here you chose L2+L3. Because you're transferring data from a single client to a single NAS. the source data is always the same, therefore the hash is always the same, therefore the Ethernet link used is always the same. That's why you're capped at the throughput of a single link.
If you want to test the gain in throughput, you need to test from multiple clients simultaneously.
jak0lantash wrote:
This is expected. LACP is good for multiple devices.
To determine which Ethernet link to send the packet through, LACP calculates a hash. Here you chose L2+L3. Because you're transferring data from a single client to a single NAS. the source data is always the same, therefore the hash is always the same, therefore the Ethernet link used is always the same. That's why you're capped at the throughput of a single link.
If you want to test the gain in throughput, you need to test from multiple clients simultaneously.
Exactly so. LACP is working as designed. If you aggregate 1 gbps links, the maximum flow to each client connection through the bond is intentionally limited to 1 gbps. That prevents packet loss at layers 1 and 2.
Your original use case was that when one "primary" user was copying a large file, all other users were blocked until that was complete. LACP should reduce how often that happens, though for each of the other user's there's still a 50-50 chance that LACP's hash will put them on the same NIC as the "primary" user creating the congestion. For those users the bandwidth starvation will still happen.
You could try a different aggregation mode (with NAS using ALB perhaps) - that has different downsides, but might work out better.
10 gigabit etherent in the server is the best technical answer, but that requires at least a 52x NAS (and of course a 10 gigabit switch).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
