c1743bed48
Summary: We'd like to make it so that it's possible to create BlobRepo that can only do writes in memory. Main motivation for that is to speed up hg changeset generation from bonsai changeset. We'd like to create all hg changesets sequentially, but store all the blobs/db entries in memory. Then we can send blobs to blobstore/rows to database in parallel. At the moment we only memory-write blobstore, this diff adds the same for bonsai hg mapping. Note that there is a method that returns all inserts in the same order as they were made. This is necessary because we need to ensure that ancestor parents are recorded before descendatns. Reviewed By: farnz Differential Revision: D10427432 fbshipit-source-id: a231c5b04734e6efeec207820d2a5b2dbef02d98 |
||
|---|---|---|
| apiserver | ||
| async-compression | ||
| asyncmemo | ||
| blobrepo | ||
| blobrepo_utils | ||
| blobstore | ||
| bonsai-hg-mapping | ||
| bonsai-utils | ||
| bookmarks | ||
| bundle2-resolver | ||
| bytes-ext | ||
| cache-warmup/src | ||
| changesets | ||
| cmdlib/src | ||
| cmds | ||
| common | ||
| docs | ||
| eden_server | ||
| failure_ext | ||
| filenodes | ||
| futures-ext | ||
| hgcli | ||
| hgproto | ||
| hook_tailer | ||
| hooks | ||
| hooks_old/src | ||
| mercurial | ||
| mercurial-bundles | ||
| mercurial-types | ||
| metaconfig | ||
| mononoke-api/src | ||
| mononoke-types | ||
| netstring/src | ||
| py_tar_utils | ||
| reachabilityindex/src | ||
| ready_state/src | ||
| repo_client | ||
| revset | ||
| server | ||
| sshrelay | ||
| storage | ||
| tests | ||
| vfs | ||
| .gitignore | ||
| .travis.yml | ||
| Cargo.toml | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| packman.yml | ||
| README.md | ||
| rustfmt.toml | ||
Mononoke
Mononoke is a next-generation server for the Mercurial source control system, meant to scale up to accepting thousands of commits every hour across millions of files. It is primarily written in the Rust programming language.
Caveat Emptor
Mononoke is still in early stages of development. We are making it available now because we plan to start making references to it from our other open source projects such as Eden.
The version that we provide on GitHub does not build yet.
This is because the code is exported verbatim from an internal repository at Facebook, and not all of the scaffolding from our internal repository can be easily extracted. The key areas where we need to shore things up are:
- Full support for a standard
cargo build. - Open source replacements for Facebook-internal services (blob store, logging etc).
The current goal is to get Mononoke working on Linux. Other Unix-like OSes may be supported in the future.