[FIX] Cargo crates with a large number of dependencies may cause slow index generation
Created:
12/18/2025 11:59:25 AM by Rich H
Status:
Awaiting Release on
Last pulled:
12/23/2025 5:45:37 PM
Description:
This can happen do to dependency lookup when generating a value for the `registry` property for dependencies.
> registry — cargo metadata uses a value of null to indicate that the dependency comes from crates.io. The index uses a value of null to indicate that the dependency comes from the same registry as the index. When creating an index entry, a registry other than crates.io should translate a value of null to be https://github.com/rust-lang/crates.io-index and translate a URL that matches the current index to be null.
CargoIndexHandler.cs line 192
Current ideas:
1. Add feed configuration value to disable checking connectors for dependencies
2. Add a feed configuration value to suggest all dependencies to be funneled through ProGet.
3. Create a custom CargoFeed method to check for packages from list of names and an optimized connector call (really just need to determine if package may exist in the feed)
4. Improved caching
Leaning towards a combination of ideas 3 and 1.