I typically run the following command to sanity-check a PR: $ mvn clean compile test-compile -am -amd -Prelease -fae -pl 'sdks/java/core'
This command takes 8 minutes (and 4 minutes with -T 1C) and I think it shouldn't take that long. I used the wonderful maven profiling tool https://github.com/takari/maven-timeline/ and it produced a timeline html that almost completely consists of running "findbugs". What can we do to ease the impact of findbugs on build performance? It seems that it's legitimately doing a bunch of stuff - applying hundreds of analyzers to thousands of classes, and taking a few ms per analyzer per class on average, which seems not unreasonable. Perhaps we can manually construct a smaller list of findbugs analyzers we actually want to run? (we should definitely keep findbugs in general - I've seen it prevent several serious bugs just in my PRs)
