A while back, we introduced the JAVA_SMALL configuration in the build, which improved build performance and reduced resource usage for several small java instances. However, it was never fully applied to all command lines where it would fit.

I have looked through the entire build and measured performance with the current "BIG" configuration vs the "SMALL" one. In all cases, the small config won, especially when measuring total user time, but also for wall clock time. The total impact on a full build is of course small, since we already hit the low hanging fruit previously, but it's still nice to take this optimization all the way.

On my Linux workstation, I save about 3 minutes of user time and a few seconds of wall clock. On a macpro, 2 minutes of user time and a few seconds of wall clock.