facebook/sapling
1
1
Fork 0
mirror of https://github.com/facebook/sapling.git synced 2024-10-10 16:57:49 +03:00
Code Issues Projects Releases Wiki Activity
a6b7e965f3
sapling/eden/scm/lib/dag/Cargo.toml

37 lines
643 B
TOML
Raw Normal View History

dag: add a library Summary: The scmdag library is going to have things related to the commit graph. Reviewed By: sfilipco Differential Revision: D15004984 fbshipit-source-id: f274cceeabae4a57985763216572f7cd055f8e07
2019-04-26 02:59:48 +03:00
[package]
name = "dag"
version = "0.1.0"
edition = "2018"
[dependencies]
indexedlog = { path = "../indexedlog" }
dag: switch from bytes to minibytes Summary: The APIs are compatible so the switch is straightforward. Reviewed By: DurhamG Differential Revision: D19818713 fbshipit-source-id: 504e9149567c90eb661804e0dad20580a401aa76
2020-02-28 20:19:41 +03:00
minibytes = { path = "../minibytes" }
dag: add a library Summary: The scmdag library is going to have things related to the commit graph. Reviewed By: sfilipco Differential Revision: D15004984 fbshipit-source-id: f274cceeabae4a57985763216572f7cd055f8e07
2019-04-26 02:59:48 +03:00
vlqencoding = { path = "../vlqencoding" }
Switch from failure::Fail trait to std::error::Error for errors Summary: This diff replaces eden's dependencies on failure::Error with anyhow::Error. Failure's error type requires all errors to have an implementation of failure's own failure::Fail trait in order for cause chains and backtraces to work. The necessary methods for this functionality have made their way into the standard library error trait, so modern error libraries build directly on std::error::Error rather than something like failure::Fail. Once we are no longer tied to failure 0.1's Fail trait, different parts of the codebase will be free to use any std::error::Error-based libraries they like while still working nicely together. Reviewed By: xavierd Differential Revision: D18576093 fbshipit-source-id: e2d862b659450f2969520d9b74877913fabb2e5d
2019-11-22 19:51:58 +03:00
anyhow = "1.0.20"
dag: add a flag storing whether a segment has roots Summary: This would allow us to implement the fast path in `children`. This is a breaking change in file format. But we haven't been really using the segmented dag format in production yet. So it's fine to not have a migration path. This potentailly makes the future format migration easier since there are 7 bits left to use. Reviewed By: markbt Differential Revision: D16976382 fbshipit-source-id: 0110c03d4ff2ce0a882b3fb8ce8ee12d2087f41f
2019-09-14 05:26:34 +03:00
bitflags = "1"
dag: add a library Summary: The scmdag library is going to have things related to the commit graph. Reviewed By: sfilipco Differential Revision: D15004984 fbshipit-source-id: f274cceeabae4a57985763216572f7cd055f8e07
2019-04-26 02:59:48 +03:00
byteorder = "1.2.7"
fs2 = "0.4.3"
dag: add logic to build high level segments Summary: High-level segments are built on top of lower level segments. We simply scan through them, and greedily pick the longest ones. Reviewed By: sfilipco Differential Revision: D15055348 fbshipit-source-id: 3b72dc766abd46669b787187b7d1d5f7171c026a
2019-05-03 23:30:29 +03:00
indexmap = "1.0.1"
dag: abstractions around remote protocols Summary: In the future the client will have a sparse IdMap, and needs the server (who has a complete IdMap)'s help to convert between Id and Slice (commit hash) for commits in the MASTER group. This diff defines basic abstractions for communications between a sparse IdMap and a complete IdMap. The basic flows are: To convert Id to Slice: Id -> Request --> Response -> Slice To convert Slice to Id: Slice -> Request --> Response -> Id (`->`: client-side; `-->`: server-side) Reviewed By: sfilipco Differential Revision: D18664206 fbshipit-source-id: 93a6b671be30ab1247c71d814817a2ea06b6bc66
2019-12-18 06:25:48 +03:00
serde = { version = "1", features = ["derive"] }
dag: add a library Summary: The scmdag library is going to have things related to the commit graph. Reviewed By: sfilipco Differential Revision: D15004984 fbshipit-source-id: f274cceeabae4a57985763216572f7cd055f8e07
2019-04-26 02:59:48 +03:00
tempfile = "3.0.7"
[dev-dependencies]
dag: move bindag from benches to a separate crate Summary: This allows bindag to be used outside benches. Reviewed By: sfilipco Differential Revision: D19503374 fbshipit-source-id: 131061f7d1d28125875a86afc330dbb9634249cf
2020-01-23 06:26:26 +03:00
bindag = { path = "bindag" }
dag: add some tests about segmentation and id assignments Summary: We now have enough building blocks to put things together. The tests are taken from the slides. Both examples and some corner cases, plus two maybe-interesting synthetic cases. There are probably more details to test. But this should give us some level of confidence. Reviewed By: sfilipco Differential Revision: D15055346 fbshipit-source-id: a76b70fec0ec7e88378830f251f997d147416db0
2019-05-03 23:30:29 +03:00
drawdag = { path = "../drawdag" }
spanset: add a benchmark of set operations Summary: This would provide some data about changes around SpanSet. Reviewed By: sfilipco Differential Revision: D15023652 fbshipit-source-id: 4cff7d1876fe20cd876f26926f31e018b6c88fd9
2019-04-26 02:59:50 +03:00
minibench = { path = "../minibench" }
dag: Add InProcessStore as iddagstore Summary: First 6 methods implemented from the IdDagStore trait for the InProcessStore. Any suggestions welcome. Reviewed By: quark-zju Differential Revision: D20499228 fbshipit-source-id: cb536a3a0136077ada78934d82a25d079a5bc809
2020-03-24 23:54:12 +03:00
once_cell = "1"
tp2/rust: update rust-crates-io Summary: The big change here is updating to quickcheck 0.9, and removing the local change to re-export `rand`. This also updates all the `rand*` crates to their current versions, which match Quickcheck's API requirements. There was quite a lot of API changes, including ascii's loss of quickcheck support. Reviewed By: dtolnay Differential Revision: D18198542 fbshipit-source-id: 31957eb8aad1d1f81c8216e8a80c2712007415c7
2019-10-31 19:38:54 +03:00
quickcheck = "0.9"
spanset: add a benchmark of set operations Summary: This would provide some data about changes around SpanSet. Reviewed By: sfilipco Differential Revision: D15023652 fbshipit-source-id: 4cff7d1876fe20cd876f26926f31e018b6c88fd9
2019-04-26 02:59:50 +03:00
[[bench]]
name = "spanset"
harness = false
dag: add benchmark about various "segment size" choices Summary: Add a benchmark testing various segment sizes - time to build segments, log size, and ancestor calcuation performance. An initial output looks like: building segment_size=4 0.223 ms segments: [34859, 10972, 3156, 834, 218, 55, 13, 3] log len: 1194609 ancestor calcuation segment_size=4 1.510 s building segment_size=8 0.193 ms segments: [34859, 5472, 737, 95, 11, 1] log len: 958272 ancestor calcuation segment_size=8 1.630 s building segment_size=10 0.213 ms segments: [34859, 4339, 460, 46, 4] log len: 918468 ancestor calcuation segment_size=10 1.739 s building segment_size=12 0.187 ms segments: [34859, 3613, 316, 26, 2] log len: 893901 ancestor calcuation segment_size=12 1.934 s building segment_size=14 0.202 ms segments: [34859, 3034, 228, 16, 1] log len: 873677 ancestor calcuation segment_size=14 2.311 s building segment_size=16 0.199 ms segments: [34859, 2601, 172, 10] log len: 858211 ancestor calcuation segment_size=16 2.139 s building segment_size=18 0.193 ms segments: [34859, 2280, 133, 7] log len: 847505 ancestor calcuation segment_size=18 2.301 s building segment_size=20 0.175 ms segments: [34859, 2043, 105, 5] log len: 839458 ancestor calcuation segment_size=20 2.335 s building segment_size=22 0.187 ms segments: [34859, 1847, 85, 3] log len: 832764 ancestor calcuation segment_size=22 2.500 s building segment_size=24 0.206 ms segments: [34859, 1668, 71, 2] log len: 826775 ancestor calcuation segment_size=24 2.570 s building segment_size=32 0.194 ms segments: [34859, 1230, 38, 1] log len: 811701 ancestor calcuation segment_size=32 3.091 s building segment_size=64 0.215 ms segments: [34859, 598, 9] log len: 790230 ancestor calcuation segment_size=64 4.215 s building segment_size=128 0.281 ms segments: [34859, 293, 2] log len: 779475 ancestor calcuation segment_size=128 7.573 s It seems segment size = 8 to 20 might be a reasonable choice. Reviewed By: sfilipco Differential Revision: D16660078 fbshipit-source-id: f8af64c703ce0209b9b4c09112c9bdc4a1371172
2019-08-10 02:12:58 +03:00
[[bench]]
dag: add dag_ops benchmark Summary: This will guide optimizations. Right now, gca_one "large sets" can take forever to run. The code to build the mozilla DAG was extracted to a single file to be sharable. Reviewed By: sfilipco Differential Revision: D16992730 fbshipit-source-id: 1538f5b0098cd06cb179bd556df285055e1d62b6
2019-09-14 05:26:34 +03:00
name = "segment_sizes"
harness = false
[[bench]]
name = "dag_ops"
dag: add benchmark about various "segment size" choices Summary: Add a benchmark testing various segment sizes - time to build segments, log size, and ancestor calcuation performance. An initial output looks like: building segment_size=4 0.223 ms segments: [34859, 10972, 3156, 834, 218, 55, 13, 3] log len: 1194609 ancestor calcuation segment_size=4 1.510 s building segment_size=8 0.193 ms segments: [34859, 5472, 737, 95, 11, 1] log len: 958272 ancestor calcuation segment_size=8 1.630 s building segment_size=10 0.213 ms segments: [34859, 4339, 460, 46, 4] log len: 918468 ancestor calcuation segment_size=10 1.739 s building segment_size=12 0.187 ms segments: [34859, 3613, 316, 26, 2] log len: 893901 ancestor calcuation segment_size=12 1.934 s building segment_size=14 0.202 ms segments: [34859, 3034, 228, 16, 1] log len: 873677 ancestor calcuation segment_size=14 2.311 s building segment_size=16 0.199 ms segments: [34859, 2601, 172, 10] log len: 858211 ancestor calcuation segment_size=16 2.139 s building segment_size=18 0.193 ms segments: [34859, 2280, 133, 7] log len: 847505 ancestor calcuation segment_size=18 2.301 s building segment_size=20 0.175 ms segments: [34859, 2043, 105, 5] log len: 839458 ancestor calcuation segment_size=20 2.335 s building segment_size=22 0.187 ms segments: [34859, 1847, 85, 3] log len: 832764 ancestor calcuation segment_size=22 2.500 s building segment_size=24 0.206 ms segments: [34859, 1668, 71, 2] log len: 826775 ancestor calcuation segment_size=24 2.570 s building segment_size=32 0.194 ms segments: [34859, 1230, 38, 1] log len: 811701 ancestor calcuation segment_size=32 3.091 s building segment_size=64 0.215 ms segments: [34859, 598, 9] log len: 790230 ancestor calcuation segment_size=64 4.215 s building segment_size=128 0.281 ms segments: [34859, 293, 2] log len: 779475 ancestor calcuation segment_size=128 7.573 s It seems segment size = 8 to 20 might be a reasonable choice. Reviewed By: sfilipco Differential Revision: D16660078 fbshipit-source-id: f8af64c703ce0209b9b4c09112c9bdc4a1371172
2019-08-10 02:12:58 +03:00
harness = false
Reference in New Issue Copy Permalink