kos13

Latest Sync Build: 1.1.70

Recommended Posts

Installing 1.0.134, already having for instanse 1.0.99 installed leaves me with the rather odd behaviour, that I need to create all shared folders all over.

On top of that, I find it problematic, that two versions can be installed at the same time.

Currently have 1.0.99 and 1.0.134 installed side by side.

This is because the name of the program changed - In version 1.0.99 it was known as "SyncApp", in later versions, such as the current 1.0.134 it is known by the new name "BitTorrent Sync"

This is the reason why you can currently have both programs installed!

Two versions of SyncApp can't be installed at the same time, neither can two versions of BitTorrent Sync, but it is possible to have an obsolete version of SyncApp and a current version BitTorrent Sync installed and running at the same time.

You should now uninstall SyncApp, leaving just BitTorrent Sync, otherwise, you're gonna run into some big problems!

Share this post


Link to post
Share on other sites

I'm running BTSync on my Raspberry Pi and Windows 8 64x.

And on both machines it says that 1.0.130 is the actual version. Are the updates slowly rolled out or is there something else wrong?

The auto-update function isn't fully working yet - you will therefore need to manually update if you want the latest version, 1.0.134

Share this post


Link to post
Share on other sites

Question: is it possible to download the same file from two hosts using to two different internet connections (e.g. Comcast 25MBps and FiOS 25MBps) if the target directory synced locally over BitTorrentSync? Does it boosts the overall loading time (25+25=50MBps)?

Thanks.

Share this post


Link to post
Share on other sites

In short: Yes.

Syncronization is based on the torrent technology so the clients send chunks not files. If I remember correctly these chunks are 4MB so if your file is bigger than 4 MB and it doesn't transfers in a few seconds then other peers will help out.

BTW supposedly Dropbox uses 4MB chunks too. What is it about this number?

Edit: I just realized you're talking about multi-WAN. With one PC this is not possible until you can bind btsync to an IP or interface or somehow balance connections, but if you virtualize another one or if you have two PCs at home then I think so. Why haven't you tried it out?

Edited by Lightning

Share this post


Link to post
Share on other sites

Question: is it possible to download the same file from two hosts using to two different internet connections (e.g. Comcast 25MBps and FiOS 25MBps) if the target directory synced locally over BitTorrentSync? Does it boosts the overall loading time (25+25=50MBps)?

Thanks.

Duplicate post - please avoid posting the same question in multiple threads

Share this post


Link to post
Share on other sites

  • It's still not possible to have read only folders -> no read-write key defined
  • it is also not possible to set custom secret of custom size. Many input fields still cap the length of the secret you can enter, please review all your input fields

Share this post


Link to post
Share on other sites

Hey BitTorrent Guys!

Since a lot of time has passed without any new release, I'm incredibly excited thinking about what may come in the upcoming version. Pleeeeeeaaaaaaasse! Let us know something! ;-)

Share this post


Link to post
Share on other sites

Hey BitTorrent Guys!

Since a lot of time has passed without any new release, I'm incredibly excited thinking about what may come in the upcoming version. Pleeeeeeaaaaaaasse! Let us know something! ;-)

The reason for the delay since the last update (1.0.134) on 15th May is due to the nature of the next update... which is big!!

The developers are making good progress on this and an update will be available "soon" (there are no specific release dates/roadmap whilst Sync is in alpha).

But since this forthcoming update to Sync has a dramatically improved core, it takes time to stabilize everything. However, according to the developers, in the forthcoming update memory consumption will be 2-3x times lower, with much better CPU utilization and network speed!

...so be patient... an update is coming and will certainly be worth the wait! :D

Share this post


Link to post
Share on other sites

in the forthcoming update memory consumption will be 2-3x times lower

That's certainly great news -- however, do you know whether it will still be linear in the number of files, though? This renders btsync a little bit obese for all those (embedded) NAS. :(

Share this post


Link to post
Share on other sites

The next build will be just the first step in memory optimization. Usually for such kind of things you have to significantly change core, so this is why the build is delayed. However changes that we made will allow us much easier remove liner growth in future builds, but not in the next one.

Keep in mind another thing, if there is no linear growth of memory - data will be stored on disk and that will mean higher CPU and slower operation. Which is desired behavior for NAS, but not for desktop.

Share this post


Link to post
Share on other sites

Great news!

I noticed the metacache directory is not deleted automatically. Can we get rid of it?

My music library will be re-indexing many-many hours and it still blocks every other share that comes after it in configuration order. I think indexing should run in two threads - one thread for one share at a time.

It seems the DHT floods (when it's disabled) are gone. Thanks.

And great job on the optimization. :)

Share this post


Link to post
Share on other sites

I noticed the metacache directory is not deleted automatically. Can we get rid of it?

Yes :)

...I agree though, it would have been good for the installer to automatically cleanup obsolete components from earlier versions!

For anyone else updating from 1.0.x builds, the "metacache" directory, on Windows, can be found under %AppData%\Roaming\BitTorrent Sync\metacache. Once you're running 1.1.x, this "metacache" folder may be safely deleted.

Share this post


Link to post
Share on other sites

There is no proxy support again :(

Oh, there are plenty of things that haven't made it into BitTorrent Sync... yet! ...because do bear in mind that it's still just in "alpha", and therefore the primary focus for the developers has been more on improving performance & stability, than on adding new features for this particular build!

Give them time, though, as proxy support is planned! ...and there's currently an 18-page "Wishlist" thread - the developers can't physically implement all of these suggestions in one go!

Share this post


Link to post
Share on other sites

is it normal for the client to re-index everything after updating? I went from 1.0.134 to 1.1.12 and the indexing has started from naught, for both my Macs.

Share this post


Link to post
Share on other sites

We changed a way we store metadata, so yes it re-index everything. Sorry for any troubles it may cause and incompatibility with older versions.

Share this post


Link to post
Share on other sites

The Linux i386 build (BitTorrent Sync 1.1.12) segfaults on my in 32bit ubuntu 13.04 machine.

I removed my old .sync directory, restarted btsync, accepted the terms of service, then segfault.

Here is the full debug log:


[~] ➔ cat .sync/sync.log
[20130511 11:44:01.480] test sha1: AE5BD8EFEA5322C4D9986D06680A781392F9A642
[20130511 11:44:01.480] test sha2: 630DCD2966C4336691125448BBB25B4FF412A49C732DB2C8ABC1B8581BD710DD
[20130511 11:44:01.480] test aes: 0A940BB5416EF045F1C39458C653EA5A07FEEF74E1D5036E900EEE118E949293
[20130511 11:44:02.506] Got 2 relay ips
[20130511 11:44:02.506] Server ip 67.215.229.106:3000
[20130511 11:44:02.506] Server ip 67.215.231.242:3000
[20130511 11:44:04.478] HTTP: IP 127.0.0.1: GET /gui/?token=DQvTfdlkzVzX-bbInRv1L4-xro3PclQ5wIKcklUZXkipVEUrd4KD43Nvt1EAAAAA&action=getsyncfolders&t=1370976244337
[20130511 11:44:06.115] HTTP: IP 127.0.0.1: GET /gui/
[20130511 11:44:06.216] HTTP: IP 127.0.0.1: GET /gui/jquery-1.8.3.js
[20130511 11:44:06.218] HTTP: IP 127.0.0.1: GET /gui/jqueryFileTree.js
[20130511 11:44:06.220] HTTP: IP 127.0.0.1: GET /gui/jquery.qrcode.min.js
[20130511 11:44:06.220] HTTP: IP 127.0.0.1: GET /gui/bootstrap.js
[20130511 11:44:06.222] HTTP: IP 127.0.0.1: GET /gui/webui.js
[20130511 11:44:06.223] HTTP: IP 127.0.0.1: GET /gui/bootstrap.css
[20130511 11:44:06.229] HTTP: IP 127.0.0.1: GET /gui/jqueryFileTree.css
[20130511 11:44:06.246] HTTP: IP 127.0.0.1: GET /gui/images/logo.png
[20130511 11:44:06.331] HTTP: IP 127.0.0.1: GET /gui/token.html?t=1370976246326
[20130511 11:44:06.387] HTTP: IP 127.0.0.1: GET /gui/?token=PgwQLRD_sKwWZb1KgaJ_WOmv5oy2tGMN5M5jTypfS8HpjSJD3DrPW_Zvt1EAAAAA&action=license&t=1370976246333
[20130511 11:44:06.387] HTTP: IP 127.0.0.1: GET /gui/icon.png
[20130511 11:44:10.849] HTTP: IP 127.0.0.1: GET /gui/?token=PgwQLRD_sKwWZb1KgaJ_WOmv5oy2tGMN5M5jTypfS8HpjSJD3DrPW_Zvt1EAAAAA&action=accept&t=1370976250775
[20130511 11:44:11.087] HTTP: IP 127.0.0.1: GET /gui/?token=PgwQLRD_sKwWZb1KgaJ_WOmv5oy2tGMN5M5jTypfS8HpjSJD3DrPW_Zvt1EAAAAA&action=getostype&t=1370976250851
[20130511 11:44:11.087] HTTP: IP 127.0.0.1: GET /gui/?token=PgwQLRD_sKwWZb1KgaJ_WOmv5oy2tGMN5M5jTypfS8HpjSJD3DrPW_Zvt1EAAAAA&action=getsettings&t=1370976250852
[20130511 11:44:11.102] HTTP: IP 127.0.0.1: GET /gui/?token=PgwQLRD_sKwWZb1KgaJ_WOmv5oy2tGMN5M5jTypfS8HpjSJD3DrPW_Zvt1EAAAAA&action=getversion&t=1370976250853
[20130511 11:44:11.171] HTTP: IP 127.0.0.1: GET /gui/?token=PgwQLRD_sKwWZb1KgaJ_WOmv5oy2tGMN5M5jTypfS8HpjSJD3DrPW_Zvt1EAAAAA&action=getostype&t=1370976251105
[20130511 11:44:11.362] HTTP: IP 127.0.0.1: GET /gui/?token=PgwQLRD_sKwWZb1KgaJ_WOmv5oy2tGMN5M5jTypfS8HpjSJD3DrPW_Zvt1EAAAAA&action=checknewversion&t=1370976251173
[20130511 11:44:11.362] HTTP: IP 127.0.0.1: GET /gui/?token=PgwQLRD_sKwWZb1KgaJ_WOmv5oy2tGMN5M5jTypfS8HpjSJD3DrPW_Zvt1EAAAAA&action=getdir&dir=&t=1370976251193

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.