Buffalo Forums

Products => Storage => Topic started by: zeecue on April 05, 2009, 11:46:10 AM

Title: LS-CHL 1TB Slow transfer?
Post by: zeecue on April 05, 2009, 11:46:10 AM
   

Hi

 

Howcome i just can transfer data to my LS-CHL with about 2800kbps over a 1000Mbps wired network, with Jumboframe support, I am connecting my pc to my LS-CHL using a Buffalo WZR-AG300NH, is there any settings i need to change on the LS-CHL or on the Router?

 

Best Regards

Morten

Title: Re: LS-CHL 1TB Slow transfer?
Post by: Dustrega on April 05, 2009, 12:51:42 PM

The original 1,518-byte MTU for Ethernet was used because of the high error rates and low speed ofcommunications. Thus, if one receives a corrupted packet, only 1,518bytes must be re-sent to correct the error. However, each framerequires that the network hardware and software process it. If theframe size is increased, the same amount of data can be transferredwith less effort. This reduces CPU utilization (mostly due to interruptreduction) and increases throughput by allowing the system toconcentrate on the data in the frames, instead of the frames around thedata. At the sender, a similar reduction in CPU utilization can beachieved by using TCP segmentation offloading,although this does not reduce the receiver CPU load.Interrupt-combining Ethernet chipsets, however, do provide most of thesame gain for the receiver, and work without special considerationwithout requiring all stations to support jumbo frames. Zero-copyNICs and device drivers, when combined with interrupt combining, canprovide effectively all the gains of jumbo frames without the re-sendcosts, and without requiring any changes to other stations on thenetwork.

 

  Whew, that's a read and a half. Anyway, long story short with jumboframes enabled on a low traffic high speed network you're actuallygoing to get a slower transfer speed. Jumbo frames work as a doubleedged sword in simple terms. When used incorrectly your transfer speed will drop at least that's what I've seen anyway. Try defaulting your ethernet frame size and see if that helps. :)

Message Edited by Dustrega on 04-05-2009 12:52 PM
Title: Re: LS-CHL 1TB Slow transfer?
Post by: zeecue on April 05, 2009, 01:32:54 PM
   I have tried all the MTUs and all have aprox the same transferspeed, both on 100 and 1000mbps network.
Title: Re: LS-CHL 1TB Slow transfer?
Post by: Dustrega on April 05, 2009, 02:04:06 PM
I notice you didn't mention a firmware version. Which one are you running?
Title: Re: LS-CHL 1TB Slow transfer?
Post by: zeecue on April 06, 2009, 09:08:54 AM
   I am running the newest, 1.07, i always check if there is a new firmware/software for a product before i ask questions about it.
Title: Re: LS-CHL 1TB Slow transfer?
Post by: Dustrega on April 06, 2009, 04:23:50 PM

My apologies I just didn't know which version you had. My recommendation if you're still experiencing slow transfer speeds would be:

 

 

If you're still experiencing transfer issues I would recommend a force firmware update and then initialize the unit immediately after.

Message Edited by Dustrega on 04-06-2009 04:25 PM
Title: Re: LS-CHL 1TB Slow transfer?
Post by: zeecue on April 07, 2009, 09:43:10 AM
   

I use STP Cat 6E cable, and only 15 feet as the longest cables, i dont get any transfer speed improvement if i just connect my pc with a crossover cable directly to the Linkstation.

Will i loose data if i initialize the unit, or if i force a firmware update? because 500gb takes a long time to transfer back and fourth, with the current speed of the linkstation.

Is the LS-XHL faster than the LS-CHL?

 

Best Regards

Morten

Title: Re: LS-CHL 1TB Slow transfer?
Post by: Dustrega on April 09, 2009, 03:01:24 PM
Loss of data should not occur on a re-initialization or force firmware update.  As far as I know there is no speed difference between the LS-XHL and LS-CHL.
Browser ID: smf (is_webkit)
Templates: 1: Printpage (default).
Sub templates: 4: init, print_above, main, print_below.
Language files: 1: index+Modifications.english (default).
Style sheets: 0: .
Hooks called: 80 (show)
Files included: 27 - 1055KB. (show)
Memory used: 733KB.
Tokens: post-login.
Queries used: 10.

[Show Queries]