Martchus/syncthing
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
Open Source Continuous File Synchronization; contains branches to build Syncthing as a C library
2,263 Commits 74 Branches 0 Tags 114 MiB
Go 82%
HTML 7.4%
JavaScript 5.3%
TypeScript 2.6%
Shell 1.7%
Other 0.9%
90a1d99785
Go to file
Jakob Borg 90a1d99785 Reuse a timer instead of allocating a new one in subscription.Poll 
This is surprisingly memory expensive when Poll gets called a lot, such
as when syncing lots of small files generating itemstarted/itemfinished
events. It's line number three in this heap profile on the
TestBenchmarkManyFiles test:

	jb@syno:~/src/github.com/syncthing/syncthing/test (master) $ go tool pprof ../bin/syncthing heap-13194.pprof
	Entering interactive mode (type "help" for commands)
	(pprof) top
	80.91MB of 83.05MB total (97.42%)
	Dropped 1024 nodes (cum <= 0.42MB)
	Showing top 10 nodes out of 85 (cum >= 1.75MB)
	      flat  flat%   sum%        cum   cum%
	      32MB 38.53% 38.53%    32.01MB 38.54%  github.com/syndtr/goleveldb/leveldb/memdb.New
	   22.16MB 26.68% 65.21%    22.16MB 26.68%  github.com/syndtr/goleveldb/leveldb/util.(*BufferPool).Get
	   13.02MB 15.68% 80.89%    13.02MB 15.68%  time.NewTimer
	    6.94MB  8.35% 89.24%     6.94MB  8.35%  github.com/syndtr/goleveldb/leveldb/memdb.(*DB).Put
	    3.18MB  3.82% 93.06%     3.18MB  3.82%  github.com/calmh/xdr.(*Reader).ReadBytesMaxInto

With this change the allocation is removed entirely.
2015-05-23 20:38:41 +02:00
assets Add .gitattributes; normalize line endings 2015-04-25 23:16:46 +09:00
cmd Support the creation of top-level folders on Windows (fixes #1822) 2015-05-21 19:21:19 +02:00
etc Drop systemd README instruction in favor of the wiki 2015-04-28 14:11:12 +02:00
Godeps Run benchmarks when running tests 2015-05-23 15:08:17 +02:00
gui Show date and time for web GUI notification (fixes #1833) 2015-05-21 19:44:45 +02:00
internal Reuse a timer instead of allocating a new one in subscription.Poll 2015-05-23 20:38:41 +02:00
protocol The protocol specs moved again 2015-01-09 08:54:19 +01:00
test Add some REST API benchmarks 2015-05-23 20:15:54 +02:00
.gitattributes Revert "Enforce line endings when cloning (fixes #1766)" 2015-05-07 22:55:31 +02:00
.gitignore hax 2015-05-11 18:39:53 +02:00
.mailmap Include ref#, show author nickname in release notes 2014-12-07 12:52:18 +01:00
AUTHORS Add cdhowie 2015-05-14 08:11:02 +02:00
authors.go Auto generate author list in gui/index.html 2015-04-04 10:09:42 +02:00
benchfilter.go Run benchmarks when running tests 2015-05-23 15:08:17 +02:00
build.go Run benchmarks when running tests 2015-05-23 15:08:17 +02:00
build.sh Run benchmarks in docker-all instead 2015-05-23 15:17:19 +02:00
changelog.go changelog.go should not be built 2015-04-20 14:03:50 +09:00
check-contrib.sh Make check-contribs a little more generous in recognizing a copyright header 2015-05-21 21:42:46 +02:00
CONDUCT.md Add Code of Conduct 2014-12-02 15:57:31 +01:00
CONTRIBUTING.md Update CONTRIBUTING to not encourage changing AUTHORS 2015-05-21 20:58:17 +02:00
LICENSE MPLv2 2015-03-17 16:02:27 +01:00
NICKS Add cdhowie 2015-05-14 08:11:02 +02:00
README.md typos and spelling correction 2015-04-29 15:59:47 +02:00

README.md

syncthing

Latest Build API Documentation MPLv2 License

This is the syncthing project which pursues the following goals:

  1. Define a protocol for synchronization of a folder between a number of collaborating devices. This protocol should be well defined, unambiguous, easily understood, free to use, efficient, secure and language neutral. This is called the Block Exchange Protocol.

  2. Provide the reference implementation to demonstrate the usability of said protocol. This is the syncthing utility. We hope that alternative, compatible implementations of the protocol will arise.

The two are evolving together; the protocol is not to be considered stable until syncthing 1.0 is released, at which point it is locked down for incompatible changes.

Getting Started

Take a look at the getting started guide.

There are a few examples for keeping syncthing running in the background on your system in the etc directory.

There is an IRC channel, #syncthing on Freenode, for talking directly to developers and users.

Building

Building Syncthing from source is easy, and there's a guide. that describes it for both Unix and Windows systems.

Signed Releases

As of v0.10.15 and onwards, git tags and release binaries are GPG signed with the key D26E6ED000654A3E (see https://syncthing.net/security.html). For release binaries, MD5 and SHA1 checksums are calculated and signed, available in the md5sum.txt.asc and sha1sum.txt.asc files.

Documentation

The syncthing documentation is on the Github wiki.

All code is licensed under the MPLv2 License.