8029cd3878
Summary: Performance looks okay comparing with tokio/bytes v0.5.4: minibytes: test clone_arc_vec ... bench: 16,542 ns/iter (+/- 1,524) test clone_shared ... bench: 16,211 ns/iter (+/- 596) test clone_static ... bench: 1,437 ns/iter (+/- 502) test deref_shared ... bench: 367 ns/iter (+/- 101) test deref_static ... bench: 366 ns/iter (+/- 1) test deref_unique ... bench: 367 ns/iter (+/- 4) test from_long_slicd ... bench: 91 ns/iter (+/- 18) = 1406 MB/s test slice_empty ... bench: 10,382 ns/iter (+/- 104) test slice_short_from_arc ... bench: 23,823 ns/iter (+/- 1,411) tokio/bytes: test clone_arc_vec ... bench: 16,213 ns/iter (+/- 1,864) test clone_shared ... bench: 18,685 ns/iter (+/- 634) test clone_static ... bench: 3,983 ns/iter (+/- 163) test deref_shared ... bench: 366 ns/iter (+/- 26) test deref_static ... bench: 373 ns/iter (+/- 36) test deref_unique ... bench: 391 ns/iter (+/- 33) test from_long_slice ... bench: 67 ns/iter (+/- 7) = 1910 MB/s test slice_empty ... bench: 15,149 ns/iter (+/- 1,708) test slice_short_from_arc ... bench: 36,541 ns/iter (+/- 3,485) clone_static is faster because minibytes don't call into vtable's clone. from_long_slice is slower because minibytes uses Arc unconditionally while bytes can avoid Arc overhead if refcount is 1. Reviewed By: DurhamG Differential Revision: D19770857 fbshipit-source-id: 5bafcc57a38c68baccfcafd3906f1a47b2bf4530 |
||
---|---|---|
build | ||
CMake | ||
common | ||
eden | ||
.gitignore | ||
.travis.yml | ||
CMakeLists.txt | ||
CODE_OF_CONDUCT.md | ||
CONTRIBUTING.md | ||
getdeps.py | ||
LICENSE | ||
make-client.py | ||
README.md | ||
rustfmt.toml |
EdenFS is a FUSE virtual filesystem for source control repositories.
EdenFS speeds up operations in large repositories by only populating working
directory files on demand, as they are accessed. This makes operations like
checkout
much faster, in exchange for a small performance hit when first
accessing new files. This is quite beneficial in large repositories where
developers often only work with a small subset of the repository at a time.
EdenFS has similar performance advantages to using sparse checkouts, but a much better user experience. Unlike with sparse checkouts, EdenFS does not require manually curating the list of files to check out, and users can transparently access any file without needing to update the profile.
EdenFS also keeps track of which files have been modified, allowing very
efficient status
queries that do not need to scan the working directory.
The filesystem monitoring tool Watchman
also integrates with EdenFS, allowing it to more efficiently track updates to
the filesystem.
Building EdenFS
EdenFS currently only builds on Linux. We have primarily tested building it on Ubuntu 18.04.
TL;DR
[eden]$ ./getdeps.py --system-deps
[eden]$ mkdir _build && cd _build
[eden/_build]$ cmake ..
[eden/_build]$ make
Dependencies
EdenFS depends on several other third-party projects. Some of these are commonly available as part of most Linux distributions, while others need to be downloaded and built from GitHub.
The getdeps.py
script can be used to help download and build EdenFS's
dependencies.
Operating System Dependencies
Running getdeps.py
with --system-deps
will make it install third-party
dependencies available from your operating system's package management system.
Without this argument it assumes you already have correct OS dependencies
installed, and it only updates and builds dependencies that must be compiled
from source.
GitHub Dependencies
By default getdeps.py
will check out third-party dependencies into the
eden/external/
directory, then build and install them into
eden/external/install/
If repositories for some of the dependencies are already present in
eden/external/
getdeps.py
does not automatically fetch the latest upstream
changes from GitHub. You can explicitly run ./getdeps.py --update
if you
want it to fetch the latest updates for each dependency and rebuild them from
scratch.
License
See LICENSE.