Compilation time doubling in Hibernate ORM

After reading https://groups.google.com/g/checker-framework-discuss/c/pLYydnOjZak/m/s2ooHiHbAQAJ i.e.

It has to do all the same work as the compiler does, such as resolving overloading and overriding, inferring generics, and type-checking.

It starts to make sense to me why using checkerframework roughly doubles compilation times.

The Hibernate ORM project is now considering to disable the checkerframework by default and only run it on CI, because it slows down our day-to-day work.

Are there any potential improvements that can reduce this overhead in the future? Or is this simply a consequence of not being able to modify the compiler directly?

We only use the NullnessChecker and I would like to understand if there might be a way to reduce the overhead of this particular analysis. Or maybe you have suggestions for alternatives since nullness analysis is the only thing we care about?

Thanks in advance!

Start by reviewing the NullnessChecker and the linked Checker Framework discussion about compilation overhead. The issue names no file, test, benchmark, or concrete acceptance criterion, so a contributor would first need to define how to measure the overhead and what improvement or alternative would count as done.