facebook/sapling
1
1
Fork 0
mirror of https://github.com/facebook/sapling.git synced 2024-10-11 01:07:15 +03:00
Code Issues Projects Releases Wiki Activity
A Scalable, User-Friendly Source Control System.
55,938 Commits 25 Branches 62 Tags 325 MiB
Rust 45.1%
Python 20.7%
C++ 10.5%
Perl 9.1%
TypeScript 7.3%
Other 7.1%
149e15f2ad
Go to file
Thomas Orozco 149e15f2ad mononoke: use spawn_future in getpack to fetch history 
Summary:
The former implementation would eagerly query Memcache when fetching history
(due to how old futures work) for files in getpack, but the new one does not.
This means the new one loses out on a lot of buffering, which the old one used
to do.

This diff emulates the old behavior by eagerly querying filenodes in getpack,
which improves performance on a very big getpack (32K files) by about 3x, and
makes it 30% faster than the old code, instead of > 2x slower.

Note that I'm not certain we really want to do this kind of aggressive
buffering in getpack long term, but for now, I'd like to keep this unchanged.

Reviewed By: StanislavGlebik

Differential Revision: D19905398

fbshipit-source-id: 49f9a2cd505a98123fd1dabb835e8e378d45c930
2020-02-27 12:34:21 -08:00
.github/workflows Add GitHub workflows configuration for Mononoke CI. 2020-02-14 12:21:00 +01:00
build Updating submodules 2020-02-26 21:11:31 -08:00
CMake eden: use third-party/rust for the vendored crates 2020-02-07 13:10:52 -08:00
common Factor our hw_port_stats_fb303 lib 2020-02-03 17:37:05 -08:00
eden mononoke: use spawn_future in getpack to fetch history 2020-02-27 12:34:21 -08:00
.gitignore mononoke: add README.md and the missing pieces for supporting cargo (#13) 2020-02-13 00:12:36 -08:00
.travis.yml Remove sudo: required from .travis.yml (#37) 2019-07-24 08:55:03 -07:00
CMakeLists.txt eden: add helper command for working with apfs 2020-02-03 16:59:17 -08:00
CODE_OF_CONDUCT.md Adopt Contributor Covenant 2019-08-29 23:23:31 -07:00
CONTRIBUTING.md mononoke: move the codebase under eden/ directory 2020-02-06 13:46:04 +01:00
getdeps.py Tidy up license headers 2019-10-11 05:28:23 -07:00
LICENSE relicense to GPLv2 2019-06-19 17:02:45 -07:00
make-client.py eden: use the zipapp_main instead of main so return code gets correctly returned 2019-12-03 09:20:42 -08:00
README.md mononoke: move the codebase under eden/ directory 2020-02-06 13:46:04 +01:00
rustfmt.toml Get rustfmt/rls working in fbcode again. 2019-09-19 18:06:23 -07:00

README.md

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.