DSM-G600, DNS-3xx and NSA-220 Hack Forum

Hello Daro,

It's seem like you have enabled jumbo frames in your DNS-320. If so, you're getting a lot of transmission errors and that's why you're having such low read speeds.

I'm not sure if DNS-320 supports jumbo frames at all. If it doesn't it's a very stupid decision from D-LINK.

Have you tried setting a smaller frame size, say 4K?

~/gnfpt

Hello,

Yes, I think you will get better performance if you set MTU to 1500 (since jumbo frames seem to be broken in DNS-320).

You can try 4K frames - smallnetbuilder.net reviews with jumbo frames are done with that MTU size
http://www.smallnetbuilder.com/index2.p … ;Itemid=54

"Once you've identified the highest packet size that works with a ping, do some testing between devices. Figure 1 showed a PC with an Intel NIC that supports frame sizes of 4088, 9014, and 16128 bytes. Your NAS options may list 4k and 9k frame sizes. In this scenario, try sending a single file to and from PC and NAS multiple times using the 4088 byte setting on the PC and the 4k setting on the NAS. Repeat the test using the 9014 and 9k settings to determine the average throughput. Throughput can be calculated by taking the file size and dividing by the seconds to transfer the file. You can do the calculation in MBytes/sec or Mbps (M bits per second); just be consistent.

As you may find, the largest size supported by both devices may not necessarily result in the fastest throughput. Limitations in PC hardware and software, as well as network hardware, can result in higher drop rates at higher frame sizes, causing excessive retransmissions and leading to lower throughput. Most of our testing on SmallNetBuilder is done using 4k jumbo frames because that's what works best with our computers and their 32 bit PCI NICs."

~/gnfpt

Daro wrote:

Hi,

I set back my pc and dns to MTU 1500. The problem is still there. I tested the mtu 9000 with ping and dns can handle the jumbo frames, but not improve the speed as the synology nas. I dont know how and why but dns read speed is less than half than write speed, what is impossible. I tried iperf and its show the opposite results, the read bandwidth was over 100MB/s and the write came back with error.
I compare the synology and dns hardware and looks like is same, but synology has newer linux version and ethernet driver can handle ipv6 addresses.

When you set MTU to 9000 you get a tremendous amount of TX errors. If you leave it at 1500, you can expect read speeds around 30-40MB/s (according to Win7).

Daro wrote:

gnfpt wrote:

When you set MTU to 9000 you get a tremendous amount of TX errors. If you leave it at 1500, you can expect read speeds around 30-40MB/s (according to Win7).

As i said i did. I set back MTU to 1500 on both the win 7 PC and DNS-320, and tested the speeds. Almost same readings. Maybe a little faster on 1500, but not significantly(1-2MB/s +). Can i check those error somewhere?

Yes, with the ifconfig on the DNS-320. For instante, your first post shows 1724 errors. When using jumbo frames this numbers increases rapidly.

To help you, I'll get NasTester and post a few number from my unit.

~/gnfpt

Probably it's due to the file mix nastest uses.
Try to transfer a large file, say an ISO, to and from the DNS-320 and check Win7 reported transfer rate to compare with my numbers.

~/gnfpt

PS: I'm assuming you have win7 or Vista.

Last edited by gnfpt (2010-12-28 19:32:59)

Daro wrote:

Yes i have win7 and i tried with some mkv files with the transfer, read and write too. DNS make about 6-7MB/s read and about 15-20MB/s write on ftp.
On totalcommander read is 3-4MB/s write is 18-22MB/s. I dont understand how can the read speed is slower than write with same settings.
and this is the nastester results

Code:

Running a 1000MB file write on drive y: once...
------------------------------
Average (W):     17,53 MB/sec
------------------------------
Running a 1000MB file read on drive y: once...
------------------------------
Average (R):     6,55 MB/sec
------------------------------

My values are completely different:

Running warmup...
Running a 200MB file write on drive W: 5 times...
Iteration 1:     22,66 MB/sec
Iteration 2:     20,75 MB/sec
Iteration 3:     22,26 MB/sec
Iteration 4:     22,76 MB/sec
Iteration 5:     21,47 MB/sec
------------------------------
Average (W):     21,98 MB/sec
------------------------------
Running a 200MB file read on drive W: 5 times...
Iteration 1:     36,95 MB/sec
Iteration 2:     35,35 MB/sec
Iteration 3:     37,99 MB/sec
Iteration 4:     32,87 MB/sec
Iteration 5:     38,36 MB/sec
------------------------------
Average (R):     36,3 MB/sec
------------------------------

I'm going to perform some tests with jumbo frames and IPV4 config and, if I manage to get a better performance, I'll let you know of my findings.

Something you could try is to use a different setup. For instance, connect the DNS-320 directly to your computer and setup static IP's and then run some tests.

My network is next:

I got a TL-WR1043ND Gigabit router, i got 2 Asus HDP-R1 mediacenter with 100Mb lan connected directly to router, and a tplink gigabit switch also connected to router. On switch there are 2 pc, the synology nas and the dns nas. And i got a notebook on wifi. So we can say pc connected directly to dns nas, or you think to connecting with a crosscabel?

egiga0    Link encap:Ethernet  HWaddr XX:XX:XX:XX:XX:XX
          inet addr:192.168.10.11  Bcast:192.168.10.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:22944637 errors:3 dropped:0 overruns:0 frame:0
          TX packets:33560751 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:532
          RX bytes:3459138578 (3.2 GiB)  TX bytes:92206619 (87.9 MiB)
          Interrupt:11

and yes DNS connected with cat5e to switch but 2 pc connected with cat6 to switch and i think the synology connected with cat5e too. I changed the synology cable with dns and nothing changed.

Could i screw something when i tried install the funplug? How can i reset the whole device? Maybe reflash the firmware? But the firmware link on dns site isnt working, and factory reset already done.

Oh and 1 more thing, i got 500 WD WD5000AAKS-00A7B HDD in RAID0, maybe the raid isnt working properly?

Last edited by Daro (2010-12-29 00:59:50)

Hi,

i tried the ifconfig 1st "ifconfig egiga0 mtu 9000 up" but this settings is lost when reboot. Then i use the /usr/local/config/config.xml edit the file

                        <jumbo_enable>0</jumbo_enable>
                        <jumbo_mtu>1500</jumbo_mtu>

to

                        <jumbo_enable>1</jumbo_enable>
                        <jumbo_mtu>9000</jumbo_mtu>

This keep the settings after reboot.

I'll try dns connect to the router directly, maybe that will the solution because 1043ND doesnt support the jumbo frames too. I will post what experience.

Last edited by Daro (2010-12-29 18:25:52)

And this when i connected with crosscabel to my PC:

Running warmup...
Running a 200MB file write on drive y: 5 times...
Iteration 1:     17,98 MB/sec
Iteration 2:     18,26 MB/sec
Iteration 3:     16,22 MB/sec
Iteration 4:     17,31 MB/sec
Iteration 5:     18,35 MB/sec
------------------------------
Average (W):     17,62 MB/sec
------------------------------
Running a 200MB file read on drive y: 5 times...
Iteration 1:     9,76 MB/sec
Iteration 2:     9,76 MB/sec
Iteration 3:     9,59 MB/sec
Iteration 4:     9,22 MB/sec
Iteration 5:     11,3 MB/sec
------------------------------
Average (R):     9,93 MB/sec
------------------------------

and when PC set back to mtu 1500

Running warmup...
Running a 200MB file write on drive y: 5 times...
Iteration 1:     16,47 MB/sec
Iteration 2:     14,32 MB/sec
Iteration 3:     16,38 MB/sec
Iteration 4:     15,74 MB/sec
Iteration 5:     16,16 MB/sec
------------------------------
Average (W):     15,82 MB/sec
------------------------------
Running a 200MB file read on drive y: 5 times...
Iteration 1:     9,8 MB/sec
Iteration 2:     9,22 MB/sec
Iteration 3:     9,29 MB/sec
Iteration 4:     10,15 MB/sec
Iteration 5:     9,84 MB/sec
------------------------------
Average (R):     9,66 MB/sec
------------------------------

Damn i forgot my transmission is working so thats why a little bit faster on direct connect to PC, because transmission cant find any tracker...

As i see i can connect to everywhere nothing changed, thats why i think something is wrong with dns, because the enviroment doesnt influence the speeds.

Last edited by Daro (2010-12-29 19:50:15)

Hello,

You're aware that in order for the changes in config.xml to work, you must reboot your device, right?
Your NAS is performing as if you're always with jumbo frames enabled.

Besides this last notes, I'm out of ideas. Format you harddrives (to remove the fun_plug) and test it again.
If it continues to perform as is, contact DLink Tech Support.

~/gnfpt

Daro wrote:

I turned off the funplug. I used only transmission and automatic and dependencies. This is the result:

Code:

Running warmup...
Running a 200MB file write on drive y: 5 times...
Iteration 1:     23,04 MB/sec
Iteration 2:     25,11 MB/sec
Iteration 3:     25,21 MB/sec
Iteration 4:     26,99 MB/sec
Iteration 5:     26,89 MB/sec
------------------------------
Average (W):     25,45 MB/sec
------------------------------
Running a 200MB file read on drive y: 5 times...
Iteration 1:     24,74 MB/sec
Iteration 2:     26,67 MB/sec
Iteration 3:     28,32 MB/sec
Iteration 4:     22,16 MB/sec
Iteration 5:     23,06 MB/sec
------------------------------
Average (R):     24,99 MB/sec
------------------------------

A little bit better but not perfect.

Is this possible? The transmission or transmission and automatic hold back the NAS so much?

Ooops it was a one time i cant reproduct this speed again...

That's odd. Your NAS seems to be capable of achieving "normal" DNS-320 speeds
Anyway, if you have a spare HD, swap your current RAID configuration with it and give it a try just to take the RAID0 and fun_plug out of the equation.

~/gnfpt

Last edited by gnfpt (2011-01-05 05:42:50)