Search the Community

Showing results for tags 'speed'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Resilio Sync
    • Sync General Discussion
    • Sync Troubleshooting
    • Sync for NAS (Network Attached Storage)
    • Sync Stories
    • Developers
    • Feature Requests

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







  1. I am running the BitTorrent Sync app (version 1.2.92; ARM) on my ReadyNAS (version 6.1.7) and the download speed is prohibitively slow. I've left it running overnight and It's been averaging about 50kB/s. It's currently connected to 3 computers on the local network (gigabit connection), all of which have full copies of the sync folder. Those computers are running Windows and OSX. I've noticed that CPU usage is quite high while syncing, with the load average hovering around 3.9 (nothing else is using any noticeable amount of CPU). I disabled the antivirus scanning on the box, which helped a little bit due to less CPU overhead, but not much. I've tried upgrading to the latest btsync version, 1.3.87, but this did not solve the problem. It actually seemed to cause more issues as the web interface would go unresponsive for long periods of time. Using Transmission to download a torrent over the internet, I reached speeds up to 3MB/s without a problem. Anyone have any ideas? Here are the logs.
  2. I am using BTsync 1.3.80 in 2 windows sites. I am now dowloading from site A to site B and it will take a few days to sync completely. The issue is that in site B the total down speed in the bottom of the app window is from 1.5 to 2 times the sum of total speed. Site B is dowloading now at a sustained rate of 210 kB/s at the bottom of the screen while the sum of the three dowloads at this time is 101 kB/s. What is the effective transmission rate? The same can be seen in site A but in the up direction. It has been behaving like this for days now. What is the explanation of that behaviour? Is BTSync using twice the amount of the effective bandwidth? Thanks Edit: Found another thread reporting this issue in version 1.3.80: so no need for this thread, sorry about that..
  3. This is happening with windows 2008 R2 and Windows 8 & 8.1, BTS 1.3.80 The transfer speed reported at the bottom of BTS screen isn't reflecting the transfer windows status. Most of the time, the value at the bottom is twice the speed that is shown in the transfer windows. As you can see in the picture below:
  4. OK folks - "seasoned network administrator" here. I've been hoping to use BTSync to share some business-related files & directories from my employer's systems, to let their clients more easily access some data, etc. But I've run into an 'Unexpected behavior!' I set up the 'server' - Windows 2008 R2 with BTSync, and share the folder. I've also set a custom 'listen port' and performed a MANUAL NAT / port forward. When the client (who is behind NAT and is *not* supporting uPNP) connects, they get a low, low speed of around 50kilobytes/second, even though the client's download pipe is many, many times that, and the server's upload pipe is many times that as well. When reviewing the open connections on each end, I could see that the 'client' was in fact NOT connecting directly to the 'server.' Is there a reason that the 'relay' servers were being used, even though there was the ability for at least a one-way direct connection? (Yes, I've tested the direct connection, by telnetting to the remote system on the custom port, and I was able to establish a connection). The configuration is fairly normal. Both systems are behind NAT firewalls. The "server" has the custom BTSync port forwarded to it. The expected behavior - direct connection from 'client' to 'server' did not happen. Why? I'm confused. Also, in the logs, I saw the following unexpected entries. Note that port "34780" is *not* the port I used - I in fact specified port 61223 - the 'lan port' it's trying to connect to is the right one, but the port it's trying to connect on the actual WAN interface is very wrong! [2014-02-13 12:59:01.296] ping xxWAN.IPxx.253.205:34780 directly[2014-02-13 12:59:01.296] ping yyLAN.IPyy.63.13:61223 peer local address[2014-02-13 12:59:02.296] Sending broadcast ping for share 5678obfuscatedshare500[2014-02-13 12:59:02.296] Sending broadcast ping for share 0123ObfucsatedShare012300071[2014-02-13 12:59:02.296] Send ping to peer (01234567obfuscatedpeer000C99) for share 0123ObfucsatedShare012300071:[2014-02-13 12:59:02.296] ping xxWAN.IPxx.253.205:34780 directly[2014-02-13 12:59:02.296] ping yyLAN.IPyy.63.13:61223 peer local address[2014-02-13 12:59:03.296] Sending broadcast ping for share 5678obfuscatedshare500[2014-02-13 12:59:03.296] Sending broadcast ping for share 0123ObfucsatedShare012300071[2014-02-13 12:59:03.296] Send ping to peer (01234567obfuscatedpeer000C99) for share 0123ObfucsatedShare012300071:[2014-02-13 12:59:03.296] ping xxWAN.IPxx.253.205:34780 directly[2014-02-13 12:59:03.296] ping yyLAN.IPyy.63.13:61223 peer local address[2014-02-13 12:59:04.297] Sending broadcast ping for share 5678obfuscatedshare500[2014-02-13 12:59:04.297] Sending broadcast ping for share 0123ObfucsatedShare012300071[2014-02-13 12:59:04.297] Send ping to peer (01234567obfuscatedpeer000C99) for share 0123ObfucsatedShare012300071:[2014-02-13 12:59:04.297] ping xxWAN.IPxx.253.205:34780 directly[2014-02-13 12:59:04.297] ping xxWAN.IPxx.253.205:34780 via relay[2014-02-13 12:59:04.297] ping yyLAN.IPyy.63.13:61223 peer local address
  5. I may not be 100% up on everything network related, but I know that when I download a torrent from a legitimate site (linux distro per say) I can max out my 30megabit connection. when I FTP with multiple threads I can also usually max out my connection and when I use HTTPS I have no issues maxing out my connection. I was excited to install btsync on a linux box that I currently SFTP into in order to retrieve files, and although the program install and setup was a breeze, it's just too slow to transfer large files on a daily basis with. I'm maxing out at 300kB (kilobytes) and I see the occasional burst to 700 or 800kB, but nothing more or steady. Is it that the protocol, being adaptive as it is, is not aggressive enough? Could there be an aggressive mode in the future or something to that nature? It would be extremely helpful to be able to download faster than I'm currently able to and really make this program shine.
  6. I have been using BitTorrent Sync for a while. I've tried many different cloud backup solutions (including several other peer-to-peer backup tools) and finally choose BitTorrent Sync and Dropbox as my cloud backup solutions. Generally speaking, BitTorrent Sync is fast once it starts to synchronize. However, I found quite often that BitTorrent Sync waits for a long time (about 5 to 6 minutes) to start synchronization. As BitTorrent Sync has no reliable way to show synchronization progress on Linux (don't trust the web UI) currently, it is very annoying for me as I constently use multiple computers at the same time. To address this issue, I even wrote a bash script to test whether a local file has been synchronized with the remote one. Dropbox on the contrast is much better on real-time synchronization. Changes on files in the Dropbox folder is almost immediately captured. I wonder whether BitTorrent Sync can do a better job to detect changes faster? Perhaps cache freqently changed files?
  7. I have read through the recent posts on slow speeds and WAN and couldn't find a solution to this one. I have a Linux server in US that is syncing to a desktop in South Africa. My old method of transfer is SFTP where I was getting speeds of 440kBs. I am on a 4MB connection this end so that was as good as it gets. Using btsync I see occasional peaks of 100kBs, but mostly it is between 20-60kBs. I have the 2 arrows in the web interface. Listening port open on both machines. I can max connection on torrent traffic on the desktop with a normal torrent client. The files sizes are generally around 20-30MB I just tried with unison the same files and have max speed. Any suggestions?
  8. I've used several P2P syncing apps in the past but they went by the wayside or grew to be very expensive. For the past couple years I've been using GoodSync (GS) and have been quite happy with it. However, when I learned of BitTorrent Sync (BTS) I just had to give it a try. Today I ran a few "low tech" tests to see how the two products compared. Here's what I found when transferring 1108 files totaling 406MB: Time To Transfer Over The Web BTS = 12 Minutes GS = 28 Minutes Time To Transfer Over A LAN BTS = 10.5 Minutes GS = 0.75 Minutes Memory Use BTS = 4.9MB GS = 9.9MB I'm thrilled with the feature set of BTS but the "over a LAN" transfer rate seems awfully slow. I'll give it another try in case something was amiss.
  9. I've seen some threads before but couldn't get any ideas where to start... So, the main issue is speed or rather the lack of it... Mostly around 2-5-10kB/s, even if I've seen shorter spikes over 100 Setup: - one-way sync from win8 machine to debian machine in another town. - 2 routers in-between, one of them over wifi (upload, ie source side) - 1 folder, 2,5K files, mostly BMP and DNG files, 58GB - interesting bit: 2/3 of that folder was already in target machine. when I "connected" them, it didn't seem to say "indexing..." as it did with another test folder (I wanted to know, if it is able to continue where other app left off) - first I tried regular cloud sync, but since I have dyndns assigned to that machine, I set up port in target router and listed server:port in source. I presume I did it correctly since the icon changed and sync works.. unfortunately, as slowly as before. With this kind of speed, it's impossible to continue as I indended to back up my photos mainly. Any ideas? Anything to check on my connection? Is it possible that service provider identifies btsync as torrent and throttles it's speed somehow?
  10. BitTorrent Sync 1.1.48 both clients on Windows (XP and Server 2008 R2). I have set it to back up my music collection one way to the internet. The total collection is 90GB in multiple folders, and many files (tens of thousands). After about 60GB uploaded (or 3 days of 24/7 uploading), the speed drops to 20KB/s, and NEVER goes higher. This is not my ISP throttling because restarting the client causes the speed to go back to maximum. If my ISP were throttling, the speed should continue to be slow after restarting the client, however this is not the case. It immediately goes to maximum speed and stays there (presumably until it craps out again). The server is more than capable of handling my upload speed from my home. The server is capable of 1 Gbps. I restarted only one client; the one on Server 2008 R2. So something is happening to cause the speed to slow down after some time.
  11. My bad. My supplier f#*& me.. Tried to delete this question. couldn't.
  12. Hi ~! I am Newbie!! kk. I had a problem, but I don't know what to do. -------------------------------------------------------------------- I want to sync very fast file system that consists of an internal network of 10 raspberry pie. We must be synchronized faster than P2P general model. So I've used the BittorrentSync but speed was very slow. Perhaps, there seems to be a limit on the maximum number of peer BittorrentSync. I want to know how that can be synchronized to the high speed by using the Bittorrent protocol. -------------------------------------------------------------------- Thx for reading. XD.