89cbb08a09
Summary: Right now, ContextConcurrencyBlobstore is instantiated in make_blobstore, which makes it a lot more effective (3 times more effective, in fact) than we want it to be, since a ticket is acquired by 3 blobstores in the chain in order to complete a put: - The multiplex - The two underlying blobstores This also has the potential to deadlock if all tickets are held by the multiplex, which results in an eventual timeout after 600s of waiting in the multiplex (this looks like it might be happening at least once or twice per hour right now on the experimental tier). In any case, the intention had always been to have one of those per repo, not one per sub-blobstore, so let's do that. The more natural place to put this seems to be the RepoBlobstore instantiation. Since I anticipate I might not be the only one who gets tripped up by this at some point, I also added a comment about this. I also updated the blobsync tests to stop re-implementing `RepoBlobstoreArgs::new()` so that adding new blobstores in RepoBlobstoreArgs will have minimal friction. Reviewed By: HarveyHunt Differential Revision: D20467346 fbshipit-source-id: a6ad2d8f04bff1c6fcaa151e947cb8af919eec07 |
||
|---|---|---|
| .github/workflows | ||
| 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.