Details
-
Improvement
-
Status: Resolved
-
P2
-
Resolution: Fixed
-
None
-
None
Description
I have collected data by running several builds against master using Gradle and Maven without using Gradle's support for incremental builds.
Gradle (mins)
min: 25.04
max: 160.14
median: 45.78
average: 52.19
stdev: 30.80
Maven (mins)
min: 56.86
max: 216.55
median: 87.93
average: 109.10
stdev: 48.01
I excluded a few timeouts (240 mins) that happened during the Maven build from its numbers but we can see conclusively that Gradle is about twice as fast for the build when compared to Maven when run using Jenkins.
Original dev@ thread: https://lists.apache.org/thread.html/225dddcfc78f39bbb296a0d2bbef1caf37e17677c7e5573f0b6fe253@%3Cdev.beam.apache.org%3E
The data is available here https://docs.google.com/spreadsheets/d/1MHVjF-xoI49_NJqEQakUgnNIQ7Qbjzu8Y1q_h3dbF1M/edit?usp=sharing
Attachments
Issue Links
- is a parent of
-
BEAM-3944 Convert beam_PerformanceTests_Python to use Gradle
- Open
-
BEAM-3942 Update performance testing framework to use Gradle.
- Resolved
-
BEAM-3943 Convert existing Java performance tests to use Gradle
- Resolved
-
BEAM-4057 Ensure generated pom don't break consumers
- Resolved
-
BEAM-4330 Sporadic ZipExceptions in tests with gradle and "isRelease"
- Resolved
- is related to
-
BEAM-3253 Gradle configurations do not declare correct inputs/outputs, requiring --rerun-tasks
- Open
- links to