⚡ Bolt: Parallelize source jar fetching #107
Conversation
Modified `SourcesJarLocator` to use `parallelStream()` for fetching source jars, significantly reducing the time spent on network I/O during dependency resolution. To support this concurrency, `GraphMemoizator` and `SourcesJarLocator` were updated to use `ConcurrentHashMap` and thread-safe operations. Also updated `SourcesLocatorTest` to ensure the test harness is thread-safe.
|
👋 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. |
💡 What: Parallelized the fetching of source jars by switching to
parallelStream()and ensuring thread-safety inGraphMemoizatorandSourcesJarLocator.🎯 Why:
SourcesJarLocatorwas performing synchronous network I/O (HEAD requests) for each dependency sequentially, which is a major bottleneck.📊 Impact: Concurrent network requests will significantly speed up the source jar resolution phase, especially for projects with many dependencies.
🔬 Measurement: Verified with
bazel test //resolver/...andexamples/local_verify_examples.sh. ConfirmedSourcesLocatorTestpasses with the new thread-safe implementation.PR created automatically by Jules for task 12842046597667519913 started by @menny