865b59eb46
Summary: Motivation for this change is the following: We want to avoid doing point lookups to the db to fetch the history, and instead select the history for a file or a directory with a single select. That should be many times faster. After we select the data from filenodes table, we need to fetch copy info data. To do that we need to either do lots of point lookups to the fixedcopyinfo (which undermines the point of doing single select) or construct a giant select statement. First option is inefficient, the second can introduce big code complexity. Instead let's add a single field that says whether we have fixed copy info or not. Db size increase should be tiny. For the data that we've already imported I'm planning to run a script that will fill the has_copyinfo field correctly. Reviewed By: jsgf Differential Revision: D8164029 fbshipit-source-id: c91c99b065808a93a9b361914cf9b3822d78cb60 |
||
---|---|---|
async-compression/src | ||
asyncmemo/src | ||
blobrepo | ||
blobstore | ||
bookmarks | ||
bookmarks_old/src | ||
bundle2-resolver/src | ||
bytes-ext | ||
cache-warmup/src | ||
changesets | ||
cmds | ||
common/pylz4/src | ||
docs | ||
eden_server/src | ||
filenodes | ||
futures-ext/src | ||
hgcli | ||
hgproto | ||
hooks/src | ||
mercurial | ||
mercurial-bundles/src | ||
mercurial-types | ||
metaconfig/src | ||
mononoke-types | ||
py_tar_utils | ||
repoinfo/src | ||
revset/src | ||
server/src | ||
sshrelay/src | ||
storage | ||
tests | ||
vfs/src | ||
.gitignore | ||
CONTRIBUTING.md | ||
LICENSE | ||
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.