RichConsolePerformanceTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
  1. … 31 more files in changeset.
Rebaseline performance tests

  1. … 29 more files in changeset.
Rebaseline performance tests

To account for recent configuration time improvements.

  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. … 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. … 29 more files in changeset.
Rebaseline all performance tests

  1. … 24 more files in changeset.
Rebaseline all performance tests

To lock in improvements based on refactorings

in the resolution engine.

  1. … 23 more files in changeset.
Rebaseline performance tests to use release snapshot, and to lock in client side performance improvements.

  1. … 23 more files in changeset.
Rebaseline all performance tests

  1. … 29 more files in changeset.
Rebaseline performance tests for large java project

This is done to lock improvements from #4396 which was the fix for

#4365.

  1. … 10 more files in changeset.
Rebaseline all performance tests

To lock in recent improvements and accept a few

minor regressions.

  1. … 29 more files in changeset.
Revert "Let Gradle 4.6 be the new performance baseline"

This reverts commit 9c1e61921d7b875af27d42a6c71918c6505d0902.

  1. … 29 more files in changeset.
Let Gradle 4.6 be the new performance baseline

  1. … 29 more files in changeset.
Rebase performance tests that involve large Java projects

There is a small regression affecting very large projects introduced

by #4255. This will be addressed with #4365 and we will provide a new

baseline for these tests after the fix.

  1. … 10 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. … 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. … 26 more files in changeset.
Updated performance tests to minimum 4.5 (#4140)

  1. … 22 more files in changeset.
Updated performance tests to minimum 4.5 (#4140)

  1. … 23 more files in changeset.
Rebaseline all performance tests

To lock in recent improvements

  1. … 22 more files in changeset.
Rebaseline performance tests

  1. … 21 more files in changeset.
Rebaseline performance improvements (#3762)

  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. … 25 more files in changeset.
Rebaseline performance tests

There has been a very small regression in startup time,

caused by supporting settings.gradle.kts files.

  1. … 13 more files in changeset.
More rebaselining of performance tests

All performance tests that use the large monolithic Java project need to be adapted.

  1. … 11 more files in changeset.
Rebaseline all performance tests

  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. … 22 more files in changeset.
Rebaseline all performance tests

The CLI startup improvements made all tests faster, so we rebaseline

them all in order to not loose this improvement again.

  1. … 23 more files in changeset.
Merge branch 'so-more-sensitive-perf-tests' into so-stable-performance-tests

  1. … 2 more files in changeset.
Rebaseline all performance tests

This is to make sure that we don't regress against the

recent improvements in performance again until 4.0 GA is out.

Once GA is out, all these baselines can be removed again, as testing

against the latest GA is the default.

  1. … 22 more files in changeset.
Add performance test for rich console in various scenarios (#2161)

    • -0
    • +55
    ./RichConsolePerformanceTest.groovy