Synology Resilio Slow until service is restarted?


Recommended Posts

I've got the latest version of Resilio (2.5.10-1)  running on my Synology DS418play which is also running the current version  (DSM 6.1.4-15217 Update 5).  I have a Resilio running on a linux server at my host and when I move files into the Linux host and the Synology starts to sync, I only get around 1.6MB/s performance.  However, if I go into the Synology and simply stop the Resilio service and then start it again, my sync speeds go to 5-6MB/s.

I've been able to reproduce this 3 times now.

It's pretty annoying to have to start/stop the service after adding files to the Resilio directory each time.  Both clients also are set to use predefined hosts and all the port forwards are correct, too.

Link to comment
Share on other sites

I am so glad that I am not the only one seeing this issue.  I have seen this exact situation happen in both FreeNAS (plugin) and UNRAID (docker).  I have tried many "fixes" with no luck as of yet.  I will update if I am able to find any solution but in the meantime I really hope someone already has one.

Link to comment
Share on other sites

24 minutes ago, 85aggie said:

I am running a relatively small UNRAID NAS server, 8T volume (5x2T).  The server has 16G of RAM which should be more than enough.

So which architecture of resilio are you using on your UNRAID?  Linux x64?  Just trying to determine if this is an issue that applies to synology or to, essentially, all linux based releases of resilio..

Edited by farrsight
wasn't thinking or reading before I posted ;)
Link to comment
Share on other sites

1 minute ago, farrsight said:

You have 16gb of ram in your Synology? Which synology?

sorry for the confusion, I realize the original post was on a Synology NAS; my response was that I am seeing the same thing on both a FreeNAS and an UNRAID NAS setup.  In my UNRAID setup, I have Resilio Sync running in a docker container and it will be transferring in speeds well below 1M/s; but after I restart the container it will immediately starts executing at speeds above 10M/s.  Over time it decreases back to under 1M/s until another restart. It operates just like software with a memory leak that will gradually start using more and more memory until a software reset (but in this case it's a bandwidth leak...)

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.