Cleanup Java performance test projects and scenarios - Sort tests into packages - Add new test projects: `largeMonolithicJavaProject`, `largeJavaMultiProject`, `mediumJavaMultiProjectWithTestNG` - Cleanup template.gradle file -- Remove "old Java" templates -- Remove unused Scala and Groovy performance test project configurations -- Remove large enterprise performance test projects - Simplify Java scenarios: clean assemble, first use, change test, getting IDE models, dependency report, abi change, non-abi change - Adjust tests to not use old test projects anymore - Add file mutators
Reduce memory for performance scenarios The scenarios should only have an amount of memory that is "reasonable" for what they are doing. This serves two purposes. It allows us to detect large memory regressions, as a reasonable upper limit will lead to lots of GC time if that limit is breached. It also makes test results more predictable, as too much memory means that many test runs will not need garbage collection at all while other test runs will have large GC cycles.