[SOLVED] Synology Cloud Station issue

[Mick]

I have a customer with a Synology DS 716+11. The staff have three laptops which are equipped with Synology's Cloud Station so that they can work from home/out-of-the-office and sync files back to the NAS. This arrangement has been running fine for several months but recently they have complained about performance problems. When I investigated, I found that on all three ltops, the CPU was threshing away at between 65 - 80%, making life very trying for the operators and punishing the fans. Synology's 'Cloud Daemon' seemed to be the culprit. Shutting this process down brought everything back to normal. However, it wasn't much of a solution, because the syncing immediately stopped, too.

I though I'd had a bit of an idea when I used Task Scheduler to start (and then stop) the Cloud Daemon for ten minutes every hour and this did work....except that, every time a file within the cloud station folders is opened, the cloud services all very kindly start themselves back up again. What's worse is that, because they weren't started by Task Manager, it can't/wont stop them. The long-term answer to this seems to be to get Synology to work on this bug. There is a thread about this over on the Sinology forums, but it is mostly just a list of people saying 'Me too...' with no input from the Company themselves.

Anyone else come across this? What I want to be able to do is have the cloud-syncing operative for - I figure - around ten minutes every hour, but then shut down again to preserve the CPU and degradation of performance. Hopefully this will just be a short-term thing and Synology will come up with a fix.

 

[ComputerRepairTech]

I saw this: https://forum.synology.com/enu/viewtopic.php?f=194&t=120352&start=30#p523210

I dunno what you should do but if theres ever a process I depend on thats resource intensive but I don't want it to slow me down I use process lasso to keep its priority low, i/o priority low, and affinity to a single thread.

Edit: oh right i forgot process hacker now has that feature where it can remember i/o priority, dont think ive tested it yet though.

 

[Mick]

I saw this: https://forum.synology.com/enu/viewtopic.php?f=194&t=120352&start=30#p523210

I dunno what you should do but if theres ever a process I depend on thats resource intensive but I don't want it to slow me down I use process lasso to keep its priority low, i/o priority low, and affinity to a single thread.

Edit: oh right i forgot process hacker now has that feature where it can remember i/o priority, dont think ive tested it yet though.

Thanks. I did try a couple of the various suggestions in that thread you linked, but with no real success. I hadn't thought of the process lasso/hacker idea. I'll give that a go - thanks.

 

[Mick]

I saw this: https://forum.synology.com/enu/viewtopic.php?f=194&t=120352&start=30#p523210

I dunno what you should do but if theres ever a process I depend on thats resource intensive but I don't want it to slow me down I use process lasso to keep its priority low, i/o priority low, and affinity to a single thread.

Edit: oh right i forgot process hacker now has that feature where it can remember i/o priority, dont think ive tested it yet though.

Just to let you know that I tried your suggestion and it worked! So well done and thanks.