ProjectCreationPerformanceTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Remove bigEmpty scenario

After consultation with @oehme, removing this scenario as it's very

unrealistic and caused a performance regression to be reported that was

not above threshold on any other scenario, all or which are more

realistic.

    • -36
    • +0
    ./ProjectCreationPerformanceTest.groovy
  1. … 1 more file in changeset.
Rebaseline all performance tests

To lock in memory usage improvements.

    • -1
    • +1
    ./ProjectCreationPerformanceTest.groovy
  1. … 32 more files in changeset.
Lock in some dependency management performance improvements

    • -1
    • +1
    ./ProjectCreationPerformanceTest.groovy
  1. … 31 more files in changeset.
Rebaseline performance tests

There is a known performance regression due to more work done during dependency resolution. Future

commits will attempt to mitigate the regression.

    • -1
    • +1
    ./ProjectCreationPerformanceTest.groovy
  1. … 31 more files in changeset.
Rebaseline performance tests

To account for a regression across most tests,

which was caused by a bugfix for lazy task creation.

Lazy task creation was only that fast because of

that bug, so this new performance level is the

expected one. We can definitely improve it further,

see https://github.com/gradle/gradle-native/issues/678

    • -1
    • +1
    ./ProjectCreationPerformanceTest.groovy
  1. … 30 more files in changeset.
Rebaseline performance tests

This change accepts a 1% regression in the

ProjectCreationPerformanceTest."create many empty projects" test.

The original baseline contains a bug that accidentaly made the

execution faster.

    • -1
    • +1
    ./ProjectCreationPerformanceTest.groovy
  1. … 31 more files in changeset.
    • -1
    • +1
    ./ProjectCreationPerformanceTest.groovy
  1. … 31 more files in changeset.
Rebaseline performance tests

    • -1
    • +1
    ./ProjectCreationPerformanceTest.groovy
  1. … 29 more files in changeset.
Rebaseline performance tests

To account for recent configuration time improvements.

    • -1
    • +1
    ./ProjectCreationPerformanceTest.groovy
  1. … 29 more files in changeset.
Lock in some performance improvements

There have been several performance improvements both in dependency management and thanks

to software model bridging.

    • -1
    • +1
    ./ProjectCreationPerformanceTest.groovy
  1. … 29 more files in changeset.
Rebaseline performance tests

- lock in recent native build improvements

- accept a minor regression in dependency resolution that will be fixed soon

- inline native baseline constant. Please use ./gradlew rebaselinePerformanceTests instead

    • -1
    • +1
    ./ProjectCreationPerformanceTest.groovy
  1. … 29 more files in changeset.
Rebaseline all performance tests

    • -1
    • +1
    ./ProjectCreationPerformanceTest.groovy
  1. … 24 more files in changeset.
Rebaseline all performance tests

To lock in improvements based on refactorings

in the resolution engine.

    • -1
    • +1
    ./ProjectCreationPerformanceTest.groovy
  1. … 23 more files in changeset.
Rebaseline performance tests to use release snapshot, and to lock in client side performance improvements.

    • -1
    • +1
    ./ProjectCreationPerformanceTest.groovy
  1. … 23 more files in changeset.
Rebaseline all performance tests

    • -1
    • +1
    ./ProjectCreationPerformanceTest.groovy
  1. … 29 more files in changeset.
Rebaseline all performance tests

To lock in recent improvements and accept a few

minor regressions.

    • -1
    • +1
    ./ProjectCreationPerformanceTest.groovy
  1. … 29 more files in changeset.
Revert "Let Gradle 4.6 be the new performance baseline"

This reverts commit 9c1e61921d7b875af27d42a6c71918c6505d0902.

    • -1
    • +1
    ./ProjectCreationPerformanceTest.groovy
  1. … 29 more files in changeset.
Let Gradle 4.6 be the new performance baseline

    • -1
    • +1
    ./ProjectCreationPerformanceTest.groovy
  1. … 29 more files in changeset.
Rebaseline performance tests on a nightly

To rule out whether the shorter version number of

the 4.5 release is leading to bias in the performance

test results. This may be due to shorter JAR names,

which lead to slightly shorter Strings in memory.

    • -1
    • +1
    ./ProjectCreationPerformanceTest.groovy
  1. … 23 more files in changeset.
Rebase all performance test to latest nightly

This version includes all changes of 4.5 GA and the changes

for 4.6 on master (merge commit 94a7230).

    • -1
    • +1
    ./ProjectCreationPerformanceTest.groovy
  1. … 26 more files in changeset.
Updated performance tests to minimum 4.5 (#4140)

    • -1
    • +1
    ./ProjectCreationPerformanceTest.groovy
  1. … 22 more files in changeset.
Updated performance tests to minimum 4.5 (#4140)

    • -1
    • +1
    ./ProjectCreationPerformanceTest.groovy
  1. … 23 more files in changeset.
Rebaseline again

Signed-off-by: Stefan Wolf <wolf@gradle.com>

    • -1
    • +1
    ./ProjectCreationPerformanceTest.groovy
  1. … 4 more files in changeset.
Rebaseline regressed performance tests

This commit rebaselines performance tests which are on the brink of

failing. We should look into those.

Signed-off-by: Stefan Wolf <wolf@gradle.com>

    • -1
    • +1
    ./ProjectCreationPerformanceTest.groovy
  1. … 4 more files in changeset.
Rebaseline performance tests

    • -1
    • +1
    ./ProjectCreationPerformanceTest.groovy
  1. … 21 more files in changeset.
Rebaseline performance improvements (#3762)

    • -1
    • +1
    ./ProjectCreationPerformanceTest.groovy
  1. … 10 more files in changeset.
Rebaseline performance tests

This accounts for recent improvements to configuration time

and dependency resolution, especially for Android builds.

    • -1
    • +1
    ./ProjectCreationPerformanceTest.groovy
  1. … 25 more files in changeset.
Rebaseline all performance tests

    • -1
    • +1
    ./ProjectCreationPerformanceTest.groovy
  1. … 23 more files in changeset.
Rebaseline all performance tests

In preparation for stricter matching, make sure

that all recent improvements are actually kept

by making them the new basseline.

    • -1
    • +1
    ./ProjectCreationPerformanceTest.groovy
  1. … 22 more files in changeset.
Rebaseline "create many empty projects"

It seems like we have a small regression which makes the build fail

sometimes. It seems not worth investigating it since it was some time

ago.

    • -1
    • +1
    ./ProjectCreationPerformanceTest.groovy