Search

Recent Posts

Tags


« | Main | »

Western Digital My Book Live 3 TB network drive

By Dale Reagan | March 15, 2012

I needed some additional storage and I was looking for:

What the Western Digital My Book provides is:

Western Digital My Book Documentation

Specifications (on my unit at least)

Configuration options/suggestions for the Mybook Disk

 

Device to Device Network Transfer Tests

 

WD 3 TD Hardware



procs -----------memory---------- ---swap-- -----io---- -system-- ----cpu----
r  b   swpd   free   buff  cache   si   so    bi    bo   in   cs us sy id wa
0  0  56448  19328  52160  58752    0    0     0     0    2   24  0  0 100  0
0  0  56448  19328  52160  58752    0    0     0     0    1   27  0  0 100  0
0  0  56448  19200  52160  58752    0    0     0     0    3   35  3  1 96  0
0  0  56448  18944  52224  58752    0    0     0    17   19   62  6  6 88  0
0  0  56448  19136  52288  58752    0    0     0    10   11   28  0  0 100  0


Western Digital My Book Live 3 TB hardware info (for my model at least)

#df -h
 Filesystem            Size  Used Avail Use% Mounted on
 /dev/md1              1.9G  986M  840M  54% /
 tmpfs                  50M     0   50M   0% /lib/init/rw
 udev                   10M  6.7M  3.4M  67% /dev
 tmpfs                  50M     0   50M   0% /dev/shm
 tmpfs                  50M  9.4M   41M  19% /tmp
 ramlog-tmpfs           20M  3.5M   17M  18% /var/log
 /dev/sda4             2.8T  1.8T 1014G  64% /DataVolume

Western Digital My Book Live 3 TB disk performance

# hdparm -Tt /dev/sda4
/dev/sda4:
 Timing cached reads:   634 MB in  2.00 seconds = 316.43 MB/sec
 Timing buffered disk reads: 350 MB in  3.01 seconds = 116.23 MB/sec

Linux Server Disk Performance

# hdparm -Tt /dev/sdb
/dev/sdb:
 Timing cached reads:   2756 MB in  2.00 seconds = 1378.12 MB/sec
 Timing buffered disk reads:  238 MB in  3.02 seconds =  78.83 MB/sec

Linux Server USB Disk Performance

# hdparm -Tt /dev/sdg

/dev/sdg:
 Timing cached reads:   2682 MB in  2.00 seconds = 1341.26 MB/sec
 Timing buffered disk reads:   78 MB in  3.06 seconds =  25.46 MB/sec

The differences between my local Linux disk performance would seem to indicate that it’s performance is LESS than the 3TB WD drive for ‘buffered disk reads’ (116 MB/sec vs 79 MB/sec.)  Figuring out the best tunings may take some time.  I am consistently seeing ~10MB/sec+ when using rsync to copy from a locally mounted remote file system to a locally mounted share on the 3TB WD drive.

Transfer bytes via Rsync

During my test I used many small files (expect this to be ‘slower’…) RX = bytes received on the 3TB gigabit network interface.  I monitored eth0 using the simple string of commands below – the captured output follows.

while [[ 1 ]] ; do printf "`date` ## " ;  ifconfig eth0 |grep bytes | awk '{print  $1, $2, $3, $4, $5, $6, $7, $8, $9}' ; sleep 5 ; done
 Wed Jan 18 13:55:37 PST 2012 ## RX bytes:2245783504 (2.0 GiB) TX bytes:475453341 (453.4 MiB)
 Wed Jan 18 13:55:42 PST 2012 ## RX bytes:2307733094 (2.1 GiB) TX bytes:475764715 (453.7 MiB)
 Wed Jan 18 13:55:48 PST 2012 ## RX bytes:2370296748 (2.2 GiB) TX bytes:476080428 (454.0 MiB)
 Wed Jan 18 13:55:53 PST 2012 ## RX bytes:2432759388 (2.2 GiB) TX bytes:476391354 (454.3 MiB)
 Wed Jan 18 13:55:59 PST 2012 ## RX bytes:2496311006 (2.3 GiB) TX bytes:476709925 (454.6 MiB)
 Wed Jan 18 13:56:04 PST 2012 ## RX bytes:2556969302 (2.3 GiB) TX bytes:477014920 (454.9 MiB)
 Wed Jan 18 13:56:10 PST 2012 ## RX bytes:2627987084 (2.4 GiB) TX bytes:477372117 (455.2 MiB)
 Wed Jan 18 13:56:16 PST 2012 ## RX bytes:2688852730 (2.5 GiB) TX bytes:477678052 (455.5 MiB)
 Wed Jan 18 13:56:21 PST 2012 ## RX bytes:2749358822 (2.5 GiB) TX bytes:477979360 (455.8 MiB)
 Wed Jan 18 13:56:27 PST 2012 ## RX bytes:2822531955 (2.6 GiB) TX bytes:478348951 (456.1 MiB)
 Wed Jan 18 13:56:33 PST 2012 ## RX bytes:2885952212 (2.6 GiB) TX bytes:478664680 (456.4 MiB)
 Wed Jan 18 13:56:39 PST 2012 ## RX bytes:2948100245 (2.7 GiB) TX bytes:478976773 (456.7 MiB)
 Wed Jan 18 13:56:44 PST 2012 ## RX bytes:3009887819 (2.8 GiB) TX bytes:479287079 (457.0 MiB)
 Wed Jan 18 13:56:50 PST 2012 ## RX bytes:3074766223 (2.8 GiB) TX bytes:479614209 (457.3 MiB)
 Wed Jan 18 13:56:55 PST 2012 ## RX bytes:3134972489 (2.9 GiB) TX bytes:479914248 (457.6 MiB)
 Wed Jan 18 13:57:01 PST 2012 ## RX bytes:3193413435 (2.9 GiB) TX bytes:480208330 (457.9 MiB)

Looking at the data above it appears that the current connection to the My Book is writing data relatively slowly – note that moving large files should yield better disk-to-disk throughput; there is a lot of overhead when moving many small files:

Since the real network throughput is always less than the theoretical maximum throughput, actual Gigabit networking transfers may be disappointing unless all system components are able to move data as quickly as possible.  Theoretical Gigabit transfers ~=: 1,000,000,000 bits per second ~= 976MB/sec, ~50 GB/min, ~300 GB/hour.  At this point, if you need something faster then USB 3 would be a better solution…  The review below indicates results of ~75GB/hour – further testing using fixed size large files would provide a better indication of maximum throughput possible with this device (i.e. see how many 5GB files can be moved in an hour.)

Measuring Network Throughput (NIC to NIC)

For this test I used ‘iperf’ on both my Linux system and the WD SAN disk.  The SAN disk was the ‘host’ (iperf -s) and the Linux system the client.  I used a simple loop and sent the output to a log file.  Using the ‘parallel’ option provides a ‘SUM’ report.  Using a ‘dummy’ file vs not using one did not seem to make much difference.  I generated a 2 GB dummy file for this test:

 

dd if=/dev/zero of=dummy.z bs=1024 count=2048
for NUM in 1 2 3 4 5 6 7 ; do iperf2 -c drbkups2012 -F dummy.z -m -P 5 | tee -a iperf.log ;  ls -l iperf.log ; done
[root@localhost]# grep SUM iperf.log |tail -6|head -5
[SUM]  0.0-10.0 sec  1.06 GBytes   911 Mbits/sec
[SUM]  0.0-10.0 sec  1.05 GBytes   904 Mbits/sec
[SUM]  0.0-10.0 sec  1.06 GBytes   911 Mbits/sec
[SUM]  0.0-10.0 sec  1.06 GBytes   905 Mbits/sec
[SUM]  0.0-10.0 sec  1.06 GBytes   906 Mbits/sec

Using Rsync the disk to NIC to disk throughput performance is quite a bit lower… (noting that the SAN disk is mounted via Samba.)

time rsync -av -W --stats --progress  dummy.z /media/WDSAN/public/Disktests/
 Download via Rsync - averages ~160+Mbits/sec
  2097152000 100%   16.10MB/s    0:02:04 (xfer#1, to-check=0/1)
  2097152000 100%   15.92MB/s    0:02:05 (xfer#1, to-check=0/1)
  2097152000 100%   16.56MB/s    0:02:00 (xfer#1, to-check=0/1)
  2097152000 100%   16.59MB/s    0:02:00 (xfer#1, to-check=0/1)
  2097152000 100%   16.72MB/s    0:01:59 (xfer#1, to-check=0/1)

Trying a simple 'cp' upload from the WDSAN:
real    1m24.979s
real    1m26.659s
real    1m25.369s
real    1m25.956s
real    1m25.483s
real    1m24.979s
Followed by download via 'cp'
real    2m46.983s
real    2m44.845s
real    2m33.766s
real    2m53.167s
real    2m44.688s
real    2m46.983s

Surprisingly, rsync ‘writes’ were only slightly slower:

real    2m5.572s |  2097152000 100%   16.08MB/s    0:02:04 (xfer#1, to-check=0/1)
real    2m5.581s |  2097152000 100%   15.97MB/s    0:02:05 (xfer#1, to-check=0/1)
real    2m7.295s |  2097152000 100%   15.78MB/s    0:02:06 (xfer#1, to-check=0/1)
real    2m7.075s |  2097152000 100%   15.79MB/s    0:02:06 (xfer#1, to-check=0/1)
real    2m6.340s |  2097152000 100%   15.88MB/s    0:02:05 (xfer#1, to-check=0/1

Measuring San Performance with Bonnie++

Since hdparm tool requires a physical drive so I opted to try bonnie++ for some additional benchmarks which will provide results for:

WD My Book Live Network Attached Hard Disk Review (External site – detail review.)

“For stress testing, we simultaneously read and wrote around 300 GB of data. Towards the end of this process (after approximately 4 hours), the maximum temperature we recorded on the chassis was 58C (the ambient temperature was 25C). However, the internal hard disk temperature reached 71C (as reported by hddtemp). The data transfer speeds also took a slight hit in order to not let the drive heat up any further. Anything above 60C is considered harmful to the health of the drive. As such, the current thermal solution in the My Book Live is not conducive to such heavy workloads. Fortunately, mainstream users considering network attached hard disks are not likely to generate such traffic.”

Topics: Computer Technology, Reviews|Comments|Feedback, System and Network Security, Unix-Linux-Os, Web Technologies | Comments Off on Western Digital My Book Live 3 TB network drive

Comments are closed.


________________________________________________
YOUR GeoIP Data | Ip: 73.21.121.1
Continent: NA | Country Code: US | Country Name: United States
Region: | State/Region Name: | City:
(US only) Area Code: 0 | Postal code/Zip:
Latitude: 38.000000 | Longitude: -97.000000
Note - if using a mobile device your physical location may NOT be accurate...
________________________________________________

Georgia-USA.Com - Web Hosting for Business
____________________________________