Quite simply because of the hardware used on the My Cloud backplane to enable the NAS for the internal My Cloud SATA hard drive there isn’t all that much you can do to improve the “speed” or “performance” of the My Cloud. Turning off most of the features (media server, remote access, etc.) and use it as a simple basic NAS device will cripple the unit for some/most users.
Fact is that unless you stop using (and turn off) media serving and several other services, the moment one copies a LOT of media files to the My Cloud the unit will get very slow/sluggish while it scans and catalogs the files being copied to the My Cloud hard drive. Turning off media serving before copying then re-enabling it post copy doesn’t really help since once enabled it will rescan the entire hard drive for media once again slowing down the My Cloud.
There are several tweaks one can perform, but again they may impact certain features of the My Cloud. They include issuing the following commands to try and deal with among other things the failure to sleep for longer than 7 to 10 minutes and occasional My Cloud sluggishness. Still doesn’t sleep much (about 30% of the time) but better than not using the commands. Do a forum search for “sleep” or “slow” and you’ll find lots of threads with lots of suggestions.
/etc/init.d/wdmcserverd stop
/etc/init.d/wdphotodbmergerd stop
/etc/rc2.d/S20restsdk-serverd stop
mount -o remount,noatime,nodiratime /dev/root /
Just a few other threads to get one started:
https://community.wd.com/t/performance-benchmark-results/151741
https://community.wd.com/t/mycloud-does-not-go-to-sleep-standby-perhaps-the-solution/158591
https://community.wd.com/t/my-cloud-never-sleeps/150904
https://community.wd.com/t/optimizing-os3-and-getting-some-sleep/96829
https://community.wd.com/t/my-cloud-slept-for-3-days-5-hours-after-killing-openvpn/96605
