-
Notifications
You must be signed in to change notification settings - Fork 426
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Fetching module extension" taking a long time to complete #2876
Comments
A big part of that time is lost in execute_cargo_tree, where for each target triple (of which there are 34 by default) triggers a The simplest solution for us at this point is to specify Considering a single cargo tree calls takes 1s to complete, it would be great to find a way to run all these computations in parallel. However, even with a single platform specified, it still takes a total of 9 seconds, so there's more to be optimized elsewhere as well. |
Hey folks,
We have a large monorepo comprising of 357 crates. We recently switched to
bzlmod
to avoid very frequent issues withCargo.bazel.lock
merge conflicts, and in that regard the transition went great.However, we're now seeing the
Fetching module extension crate in @@rules_rust~//crate_universe:extension.bzl; starting
step taking from a minimum of 20s to upwards of two minutes. This runs on anybazel build
orbazel mod deps --lockfile_mode=update
provided one or moreCargo.toml
declared in themanifests
key of.from_cargo
istouch
ed, which occurs very frequently.Is there a way we could speed up this step in our configuration?
This is our
MODULE.bazel
file:The text was updated successfully, but these errors were encountered: