jeanbisutti commented on pull request #2: URL: https://github.com/apache/maven-dist-tool/pull/2#issuecomment-817180254
@slachiewicz `We asked here quick-perf/maven-test-bench#18 to maybe add code to our tool to do perf tests and have our reports also - would it be possible to implement?` quick-perf/maven-test-bench#18 proposes to "ingest daily Maven memory check to daily Maven dist-tool report", I don't see the mention of performance tests addition. From what I understand from maven-dist-tool Readme and code, it aims at producing a report. The performance information is _automatically_ generated _each day_ in the following way: * The Maven head is checkouted and a Maven distribution is built from it * A specific version of Apache Camel is checkouted, a massive multi module project * `mvn validate` is applied on this project, and the heap allocation is checked Control and reduce heap allocation seem an important matter for Maven project. Indeed, a part of the heap allocation will be garbage collected and the garbage collection activity is succeptible to slow down the build. Also, less heap allocation means that we may execute Maven with a smaller heap size. Having a daily check on Maven heap allocation may help the Maven development because: * It would be possible to be comfortable that each new code modification does not lead to a significant increase of heap allocation, so it would not be needed to manually launch a heap bench of a new Maven distribution (for example with Maven 3.8.1 and 4.0 snasphot) * Having a regular check would ease the identification of the code causing a significant increase of heap allocation -- 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. For queries about this service, please contact Infrastructure at: [email protected]
