149e15f2ad
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 |
||
|---|---|---|
| .. | ||
| apiserver | ||
| benchmark | ||
| blobimport_lib/src | ||
| blobrepo | ||
| blobrepo_utils | ||
| blobstore | ||
| blobstore_sync_queue | ||
| bonsai_git_mapping | ||
| bonsai_globalrev_mapping | ||
| bonsai_hg_mapping | ||
| bookmarks | ||
| cache_warmup/src | ||
| changesets | ||
| cmdlib | ||
| cmds | ||
| commit_rewriting | ||
| common | ||
| derived_data | ||
| edenapi_server/src | ||
| fastreplay/src | ||
| filenodes | ||
| filestore/src | ||
| git | ||
| gotham_ext/src | ||
| hgcli | ||
| hgproto | ||
| hook_tailer | ||
| hooks | ||
| lfs_import_lib/src | ||
| lfs_protocol | ||
| lfs_server/src | ||
| manifest | ||
| mercurial | ||
| metaconfig | ||
| mononoke_api/src | ||
| mononoke_types | ||
| newfilenodes | ||
| phases | ||
| pushrebase/src | ||
| reachabilityindex | ||
| repo_client | ||
| revset | ||
| scs_server/src | ||
| segmented_changelog/src | ||
| server | ||
| sshrelay | ||
| tests | ||
| walker/src | ||
| Cargo.toml | ||
| README.md | ||
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.
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