.editorconfig

rust-nodemap: pure Rust example

To run, use `cargo run --release --example nodemap`

This demonstrates that simple scenarios entirely written
in Rust can content themselves with `NodeTree<T>`.

The example mmaps both the nodemap file and the changelog index.
We had of course to include an implementation of `RevlogIndex`
directly, which isn't much at this stage. It felt a bit
prematurate to include it in the lib.

Here are some first performance measurements, obtained with
this example, on a clone of mozilla-central with 440000
changesets:

  (create) Nodemap constructed in RAM in 153.638305ms
  (query CAE63161B68962) found in 22.362us: Ok(Some(269489))
  (bench) Did 3 queries in 36.418µs (mean 12.139µs)
  (bench) Did 50 queries in 184.318µs (mean 3.686µs)
  (bench) Did 100000 queries in 31.053461ms (mean 310ns)

To be fair, even between bench runs, results tend to depend whether
the file is still in kernel caches, and it's not so easy to
get back to a real cold start. The worst we've seen was in the
50us ballpark.

In any busy server setting, the pages would always be in RAM.

We hope it's good enough not to be significantly slower on any
concrete Mercurial operation than the C nodetree when fully in RAM,
and of course this implementation has the serious headstart advantage
of persistence.

Differential Revision: https://phab.mercurial-scm.org/D7797

# See http://EditorConfig.org for the specification

root = true

[*.py]
indent_size = 4
indent_style = space
trim_trailing_whitespace = true

[*.{c,h}]
indent_size = 8
indent_style = tab
trim_trailing_whitespace = true

[*.t]
indent_size = 2
indent_style = space
trim_trailing_whitespace = false