⚡ Bolt: Parallelize source JAR resolution #103
Conversation
💡 What: - Switched `SourcesJarLocator` to use `parallelStream()` for fetching source JARs. - Upgraded `GraphMemoizator` and `SourcesJarLocator` caches to `ConcurrentHashMap` for thread safety. - Used `computeIfAbsent` for atomic cache operations. 🎯 Why: - Source resolution involves making network `HEAD` requests to check for the existence of `-sources.jar` artifacts. Doing this sequentially for large dependency graphs is a significant bottleneck. 📊 Impact: - Expected to significantly reduce resolution time for projects with many dependencies by performing network I/O in parallel. 🔬 Measurement: - Verify that `bazel test //resolver/...` passes (ensuring thread safety didn't break logic). - Verify that the resolver still correctly identifies source JARs. Bolt ⚡ performance improvement.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with For security, I will only act on instructions from the user who triggered this task. New to Jules? Learn more at jules.google/docs. |
Parallelize source JAR resolution to improve performance.
PR created automatically by Jules for task 7277791992055648861 started by @menny