3TB My Book Live feedback - slow wired backups

I received my My Book Live from Amazon on Friday so I’ve spent most of the weekend playing with it backup up my systems – I have a couple Macbook Pros and a Windows desktop to back up along with a smallish media library I’ll stream to my TV using a WD media player.  Fairly simple setup.

But, backups have seemed to be painfully slow - I’m not backing up over wifi - I was to the point of getting perhaps < 1MB/s on a 40G backup.  So, I enabled ssh and started poking around – the sleep mode monitoring service was competing with the smbd process for the disk – and being that this thing only has 256MB of RAM, having twonky and all these other services running along with the HUGE apache/php footprint, I think the system is just starved for memory.  Disabling twonky and sleep mode (manually killing the monitorio.sh process) and stopping apache and nfs (not using nfs anyway) really seems to have made a big difference.

The backup I’m running from my Macbook Pro now seems to be going pretty well getting 10-20MB/s (note I’m going through a 10/100 switch in this room, so plugging into the GigE switch the NAS is plugged into might make it go even faster).

So my feedback is that some optimizations could be made in the firmware to give more free memory to the kernel to deal with the huge drives in these things – the apache stack could perhaps be replaced with nginx,  and there should be a way to disable nfs in the UI (is there already?), and there should be a better way to sleep the disk than crawling the whole filesystem…


mbillens1, your post sounds more like a good Feature Request; the best place for this, is in the Ideas Exchange section. This way someone from WD will be sure to see it and will allow more users to support your idea.

However, I would first search and make sure that there are no other active Feature Requests suggesting the same or similar improvements. If there is, then you could add your post and vote on it.

Network Drive Ideas


Thanks, put this up here:   http://community.wdc.com/t5/Network-Drive-Ideas/Optimizing-memory-footprint/idi-p/254640


Which process needs to be killed to stop nfs?  Also wondering if there is a script witnin /etc/init.d to start and stop the NFS service?  Plus, is there a script to stop AFS as I don’t use that.  Will there be something within /etc/init.d?

Just to stop the service.  I can live with having to keep stopping those two services on each reboot of my NAS, but is stays on 99.9% of the time so not much of an issue having to stop services each time.