Martin von Zweigbergk d989d4093d merged_tree: let backend influence whether to use new diff algo ... Since the concurrent diff algorithm is significantly slower when using the Git backend, I think we'll have to use switch between the two algorithms depending on backend. Even if the concurrent version always performed as well as the sequential version, exactly how concurrent it should be probably still depends on the backend. This commit therefore adds a function to the `Backend` trait, so each backend can say how much concurrency they deal well with. I then use that number for choosing between the sequential and concurrent versions in `MergedTree::diff_stream()`, and also to decide the number of concurrent reads to do in the concurrent version.		2023-11-06 23:12:02 -08:00
..
benches	cargo: rename crates from jujutsu/jujutsu-lib to jj-cli/jj-lib	2023-07-09 06:40:43 +02:00
gen-protos	Use { workspace = true } to appease VS Code's Cargo.toml parser	2023-08-22 21:38:53 -07:00
src	merged_tree: let backend influence whether to use new diff algo	2023-11-06 23:12:02 -08:00
tests	merged_tree: let backend influence whether to use new diff algo	2023-11-06 23:12:02 -08:00
testutils	merged_tree: let backend influence whether to use new diff algo	2023-11-06 23:12:02 -08:00
Cargo.toml	async: switch to pollster's block_on()	2023-11-03 08:15:10 -07:00
LICENSE	cargo: add LICENSE file to each crate we publish	2023-09-22 21:48:28 -07:00