Jun Wu 75e4ffc17f indexedlog: change IndexDef.lag_threshold back from entries to bytes ... 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		2020-03-05 13:29:48 -08:00
..
src	indexedlog: change IndexDef.lag_threshold back from entries to bytes	2020-03-05 13:29:48 -08:00
Cargo.toml	Switch from failure::Fail trait to std::error::Error for errors	2019-11-22 08:53:31 -08:00