A large Java based build to use when benchmarking and profiling Gradle
Groovy Java Shell
Latest commit 7a8d1e1 Feb 7, 2017 @jjohannes jjohannes Adjust PerformanceTestGenerator for Gradle 3.4
The Java plugin now has configurations that can not be resolved.
We exclude these in the `resolveConfigurations` task.


Large Enterprise Performance Reproduction Project

Getting Started

Clone the repo:

$> git clone https://github.com/gradle/perf-enterprise-large.git
$> cd perf-enterprise-large

From here you need to run the generation script. It takes about 30 seconds to do it's work.

$> ./setup.sh

Copy gradle.properties.sample as gradle.properties

$> cp gradle.properties.sample gradle.properties

At this point, you should be able to run the build.

$> gradle -g gradle-user-home resolveDependencies

Testing downloading

Remove the gradle-user-home directory and create a new one to test downloading from a clean state.

$> rm -rf gradle-user-home
$> mkdir gradle-user-home

Make sure to pass -g gradle-user-home to the gradle command.

$> gradle -g gradle-user-home resolveDependencies

Enabling access logging for maven-server

$> export MAVEN_SERVER_ACCESS_LOG=$PWD/maven-server.log

Benchmarking and profiling

Use the Gradle profiler to --benchmark or --profile scenarios. The available scenarios are defined in performance.scenarios

Example usage: ./gradle-profiler --profile chrome-trace buildUpToDate