mirror of
https://github.com/facebook/sapling.git
synced 2024-10-10 08:47:12 +03:00
75e4ffc17f
Summary: I thought the index function could be the bottleneck. However, the Log reading (xxhash, decoding vlqs) can be much slower for very long entries. Therefore using bytes as the lag threshold is better. It does leaked the Log implementation details (how it encodes an entry) to some extend, though. Reverts D20042045 and D20043116 logically. The lagging calculation is using the new Index::get_original_meta API, which is easier to verify correctness (In fact, it seems the old code is wrong - it might skip Index flushes if sync() is called multiple times without flushing). This should mitigate an issue where a huge entry (generated by `hg trace`) in blackbox does not get indexed in time and cause performance regressions. Reviewed By: DurhamG Differential Revision: D20286508 fbshipit-source-id: 7cd694b58b95537490047fb1834c16b30d102f18 |
||
---|---|---|
.. | ||
src | ||
Cargo.toml |