Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[lizzi555]

@Robocub
Great result 37-38 MB/s !

That inspired me to also test my devices.

http://lizzi555.dyndns.org/Speed/Speedtest_en.html

If you know the trick with the DNS, please tell us 

[Robocub]

I honestly can't say there's any trick, not that I know. FWIW, make sure you're using short length cat5e or cat6 ethernet cables. I'm using cat5e and very short lengths since all my gear is within 3 feet of each other. I believe anything graded less than 5e will not work well with gigabit.

[fordem]

Once again you apparently miss my point.  I was only trying to point out that nothing in my system should be limiting the speeds from the NAS.  I have gigabit with jumbo frames and a sufficiently fast processor writing to a 10k RPM Raptor drive.  I'm just trying to figure out why some folks get the faster transfer speeds being reported here.

I didn't miss your point - on the other hand - you, despite being pointed directly at the probable bottleneck, failed to see it.

So that you recognize it, I'm one of those folks reporting transfer speeds faster than your "mid 20s" highest, and I'm doing it with significantly less processing power, and by the way, 7200 rpm disks - and - I'm pointing out to you that in your previous post you focused on your jumbo frame equipped network and superfast processor, but ignored the disk subsystem.

Well - if I run a test that ignores the disk subsystems I can clock even higher throughput - how does 50MBytes/sec grab you?  That by the way is at the "flea powered" DNS-323 end, if I switch to the 3.0GHz HT side of things, that becomes 800MBytes/sec.

With this sort of throughput across the network, what is it that limits the throughput when I'm writing to the disks - well - how about the disk subsystem.

It's there in my previous post - your disk subsystem is the potential limiting factor - and please try to understand the difference between the disk subsystem and the disk itself - the subsystem includes such essentials as the disk interfaces or controllers and the drivers for them, things that so many people take for granted.

[gunrunnerjohn]

I really don't get your point now.  My disk subsystem on this system is able to sustain 70mbyte/sec local copies, so clearly that's not the issue.  As far as the DNS-323, it has a pair of Samsung 1.5TB drives, and they will certainly do better than the mid 20's.

Maybe the problem is you're not really being specific as to which end you feel is the bottleneck.  Since we all have the same DNS-323, I have to believe you somehow believe it's my system, and that doesn't compute.

[JurgenBraun]

I just got the DNS323, and I also experience very slow file transfers. I have a fairly straightforward setup, Windows 7, everything on gigabit switch, jumboframes enabled. When I copy large directories from one disk to another, I get speeds around 2 to 3 MB/sec. I didn't load any additional drivers, just the "net use" command to map the drives. Is there anything else to load or enable? Also, is there a utility that allows a direct copy from one drive to another, without going through an external computer? I tried the backup command for this, (backing up one directory to the other drive in the DNS 323) but didn't get fatser speeds either. Something must be wrong. Thanks for any ideas.

[fordem]

JurgenBraun

It's been my experience that copying "large directories" containing large numbers of small files is significantly slower than copying a similar quantity of data in a single file - this may be the cause of your slow transfers.

[gunrunnerjohn]

My tests have been copying a large file of about a gigabyte in size.