seaweedfs/.git - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author	Files	Lines
2016-06-02	directory structure change to work with glide	Chris Lu	1	-134/+0
	glide has its own requirements. My previous workaround caused me some code checkin errors. Need to fix this.
2016-04-10	Revert "Merge pull request #284 from thinxer/binary"	chrislusf	1	-8/+8
	This reverts commit 3523ad523929870aa8d4a7741ee8e152cfd40489, reversing changes made to 5d100994b1b9c6679113c8dd73f97aff85397f02.
2016-04-09	replace util/bytes.go with binary.BigEndian	Jianfei Wang	1	-8/+8

2016-04-08	Revert "Merge pull request #281 from thinxer/binary"	chrislusf	1	-8/+8
	This reverts commit a87fe8ffcec7a5210bf97301e2951eea51a0a0ec, reversing changes made to 6876bfa68524d4fc0a961f89dc29e53fbc654ea5.
2016-04-06	replace util/bytes.go with binary.BigEndian	Jianfei Wang	1	-8/+8

2015-05-26	Add "weed backup" command.	chrislusf	1	-21/+5
	This is a pre-cursor for asynchronous replication.
2015-04-16	Change all chrislusf/weed-fs links to point to chrislu/seaweedfs	Stuart P. Bentley	1	-2/+2

2015-03-29	Add boltdb for volume needle map	chrislusf	1	-3/+2
	boltdb is fairly slow to write, about 6 minutes for recreating index for 1553934 files. Boltdb loads 1,553,934 x 16 = 24,862,944bytes from disk, and generate the boltdb as large as 134,217,728 bytes in 6 minutes. To compare, for leveldb, it recreates index in leveldb as large as 27,188,148 bytes in 8 seconds. For in memory version, it loads the index in To test the memory consumption, the leveldb or boltdb index are created. And the server is restarted. Using the benchmark tool to read lots of files. There are 7 volumes in benchmark collection, each with about 1553K files. For leveldb, the memory starts at 142,884KB, and stays at 179,340KB. For boltdb, the memory starts at 73,756KB, and stays at 144,564KB. For in-memory, the memory starts at 368,152KB, and stays at 448,032KB.
2015-03-27	add leveldb support for needle map	chrislusf	1	-0/+151
	This supposedly should reduce memory consumption. However, for tests with millions of, this shows consuming more memories. Need to see whether this will work out. If not, later boltdb will be tested.