rmuir opened a new issue, #14911:
URL: https://github.com/apache/lucene/issues/14911
### Description
on my machine, running precommit:
```
Aggregate task times (possibly running in parallel!):
134.47 sec. ecjLintMain
123.87 sec. ecjLintTest
108.09 sec. checkGoogleJavaFormat
69.68 sec. compileTestJava
68.44 sec. compileJava
25.70 sec. validateSourcePatterns
13.54 sec. rat
11.98 sec. forbiddenApisTest
11.98 sec. applyEcLint
11.73 sec. forbiddenApisMain
8.83 sec. applyAstGrepRules
7.16 sec. jar
6.77 sec. pluginUnderTestMetadata
4.26 sec. ecjLintTools
3.60 sec. resolveConfigurationGroups
```
I added timing output to the ecj: I don't see anything especially slow,
instead the accumulated time seems to be "death by a thousand stabs", the
fork()'ing cost of spinning up 2 jvms for each module (source, test).
So I don't know if its reasonable, or a good idea, to see if ecj compiler
can work as "compiler plugin" or use some gradle "compiler api" (e.g. `fork =
false`). It might save a ton of overhead.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
