April 1, 201115 yr Hi There, When I copy files to the share on the array, from my Win7 64 bit client, the speed is about 25 MB/s is that normal? The array consists of 3 WD EARS 2T (one of them is parity). I'm running unRAId v 4.7. Thanks.
April 1, 201115 yr are the drives jumpered or un-jumpered are they precleared with or without -A what is your MBR set to?
April 1, 201115 yr Hi There, When I copy files to the share on the array, from my Win7 64 bit client, the speed is about 25 MB/s is that normal? The array consists of 3 WD EARS 2T (one of them is parity). I'm running unRAId v 4.7. Thanks. It might, depending on everything involved. Factors influencing the speed are: The source disk The disk driver on the source PC The activity on the source PC The network card on the source PC The network driver on the source PC The LAN cables involved. The router/switch involved The other activity on the LAN Induced noise on the LAN (proximity to power cables,lack of shielding) The network card/chipset on the unRAID server. The network driver on the unRAID server The rotational disk speed of the disks being written to on the unRAID server. 5400 RPM green drives will be a third slower in writing than 7200 RPM non-green drives. Other activity on the unRAID server. (Is it doing its monthly parity check, that will share the buss bandwidth for writing.) So... the answer to your question is... we have no clue... Your performance is not bad, but not as high as someone with a really good LAN and an otherwise idle source PC and an otherwise idle unRAID server that are both tweaked for highest performance with 7200 RPM drives throughout and no PCI bus contention. The rotational speed ratio between 7200 and 5400 RPM drives is 1.33 to 1. If you have any "green" drives, they will get 75% of the speed I can get with all 7200 RPM drives. I get between 35 and 40 MB/s. 35 MB/s * .75 = 26.25 MB/s. You are not that far off. Joe L.
April 1, 201115 yr I had very similar speed with the exact same disks from different W7/32bit workstations. I have just recently changed the parity to Seagate Barracuda Green ST2000DL003 (5900rpm) and unjumpered and precleared the 2TB EARS that was parity before and replugged it to replace a 400GB disk. Speed virtually unchanged and very close to yours. It's probably what you get with unRAID and those disks.
April 1, 201115 yr Author This is a new server build. The WD EARS drives are un-jumpered and they are precleared with -A (over 30 hours to complete). I have a Gigabit network. A speed disk test on the array will show: /dev/sda: Timing cached reads: 7746 MB in 2.00 seconds = 3875.91 MB/sec Timing buffered disk reads: 338 MB in 3.00 seconds = 112.60 MB/sec /dev/sdb: Timing cached reads: 7692 MB in 2.00 seconds = 3848.95 MB/sec Timing buffered disk reads: 362 MB in 3.01 seconds = 120.18 MB/sec /dev/sdc: Timing cached reads: 7776 MB in 2.00 seconds = 3890.08 MB/sec Timing buffered disk reads: 328 MB in 3.01 seconds = 109.02 MB/sec ---------------- The fdisk -lu results: # fdisk -lu /dev/sda Disk /dev/sda: 2000.3 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 64 3907029167 1953514552 83 Linux Partition 1 does not end on cylinder boundary. root@Tower:~# fdisk -lu /dev/sdb Disk /dev/sdb: 2000.3 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdb1 64 3907029167 1953514552 83 Linux Partition 1 does not end on cylinder boundary. root@Tower:~# fdisk -lu /dev/sdc Disk /dev/sdc: 2000.3 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdc1 64 3907029167 1953514552 83 Linux Partition 1 does not end on cylinder boundary. --------- The ethtool eth0 will show: # ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes Thanks.
April 1, 201115 yr I just recently upgraded my source drive from an older IDE drive to a slightly less old 7200RPM SATA drive and gained approx. 10 MB/s on transfers... In my own experience, this has been the biggest speed improvement for me. I also upgraded the Cache drive to a slightly faster drive, but saw much less of an improvement. Also, try using a cache drive. It should add more 'perceived' speed to your transfers...
April 1, 201115 yr If parity is in place and running 25MB/sec is actually pretty good without a cache drive in place when copying to the user share.
April 1, 201115 yr Author Yes it is 1 parity drive and 2 data drives (WD EARS). If I add a share drive how much speed improovement I will see? Which is the suggested shared drive in this case?
April 1, 201115 yr Do you mean a cache drive? The write speed will be limited by the speed of the cache drive or the network. See this thread: http://lime-technology.com/forum/index.php?topic=5754.0
April 1, 201115 yr Author Yes, sorry I mean a cache drive. I will do that and see if there is a speed improovement as expected.
April 2, 201115 yr 25MB/s is the speed I got when I put an 2T EARS drive in and it was unjumpered aligned to 63. When I pulled it, pre-cleared setting to 64 aligned, I got back to my normal 30-35MB/s write (which I think is the top end for most anyone's unraid box when directly writing with parity). If you want faster, I get 60-70MB/s writing to a WD Black cache drive
April 2, 201115 yr I think I'm getting 25-28 with an all Green drive configuration. I figure its completely fine knowing its protected, but my reading is much faster which is very important for multiple video streams.
April 2, 201115 yr I think I'm getting 25-28 with an all Green drive configuration. I figure its completely fine knowing its protected, but my reading is much faster which is very important for multiple video streams. I have an all green drive config with no cache drive and those are right about what my writes are.
April 3, 201115 yr Author Thanks, it looks like that ~25 Mb/s is normal speed with green drives. I should get a WD black cache drive to improove write speed.
April 3, 201115 yr Do you really need faster than 25mb? I normally right a few files a day and well the rest are all reading.
April 5, 201115 yr Author Hi Guys, I would like to mention that after ussing a WD EARS green cache drive and performing the following jumbo frames twick, I now get ~90MB/s to 100MB/s transfer speeds. ifconfig eth0 mtu 6000 That is a huge improvement.
April 5, 201115 yr Hi Guys, I would like to mention that after ussing a WD EARS green cache drive and performing the following jumbo frames twick, I now get ~90MB/s to 100MB/s transfer speeds. ifconfig eth0 mtu 6000 That is a huge improvement. Sure, maybe for the burst speed, but you'll have to supply proof of that being a sustainable speed when transferring very large multi gigabit sized files before I'll believe you. Peter
April 5, 201115 yr Hi Guys, I would like to mention that after ussing a WD EARS green cache drive and performing the following jumbo frames twick, I now get ~90MB/s to 100MB/s transfer speeds. ifconfig eth0 mtu 6000 That is a huge improvement. Did you also set the mtu on your PC?
April 5, 201115 yr Hi Guys, I would like to mention that after ussing a WD EARS green cache drive and performing the following jumbo frames twick, I now get ~90MB/s to 100MB/s transfer speeds. ifconfig eth0 mtu 6000 That is a huge improvement. When you say transfer speeds I assume you just mean reading from a drive on unraid and not writing to a parity protected drive.
April 6, 201115 yr Author Hi Guys, I would like to mention that after ussing a WD EARS green cache drive and performing the following jumbo frames twick, I now get ~90MB/s to 100MB/s transfer speeds. ifconfig eth0 mtu 6000 That is a huge improvement. When you say transfer speeds I assume you just mean reading from a drive on unraid and not writing to a parity protected drive. This is writing using a cache drive. I did transfer more files about ~1TB and the speed was steady 75 MB/s to 80 MB/s
April 6, 201115 yr Author Hi Guys, I would like to mention that after ussing a WD EARS green cache drive and performing the following jumbo frames twick, I now get ~90MB/s to 100MB/s transfer speeds. ifconfig eth0 mtu 6000 That is a huge improvement. Did you also set the mtu on your PC? No, I didn't. Only on the unRAId server.
April 6, 201115 yr Author One correction to the cache drive used. It is the Seagate ST2000DL003 and not the WD EARS as mentioned earlier.
Archived
This topic is now archived and is closed to further replies.