maven indexing: local repo indexing optimizations #4095
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
flamegraphs showed that ClassDependencyIndexCreator.addDependencyToMap
had some potential for optimizations.
but also slightly more readable code IMO
stateful impl (MatchWords), the JVM is likely very good at
optimizing/vectorizing String intrinsics
benchmark showed ~20% speedup
full indexing takes on my system and with my current local maven repo ~53s (down from ~66s)
@timboudreau what is your opinion on this? You wrote most of the original optimizations (including the
MatchWords
class). I can't see you in the reviewer list for some reason.sidenote:
I did also write a parallel version using an
ExecutorService
which could reduce it further to ~38s, but it made the code slightly more complex which is probably not worth the trouble. Parallelizing on a higher level (outside ofClassDependencyIndexCreator
) might give better results (better scaling) since this is only a small slice of the task.flamegraphs: