JavaConfigurationPerformanceTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Rebaseline JavaConfigurationPerformanceTest

    • -1
    • +1
    ./JavaConfigurationPerformanceTest.groovy
Remove newlines added by IDEA

    • -1
    • +0
    ./JavaConfigurationPerformanceTest.groovy
  1. … 14 more files in changeset.
Convert some easy classes to use Gradle profiler

    • -2
    • +3
    ./JavaConfigurationPerformanceTest.groovy
  1. … 18 more files in changeset.
Convert some easy classes to use Gradle profiler

    • -2
    • +3
    ./JavaConfigurationPerformanceTest.groovy
  1. … 19 more files in changeset.
Convert some easy classes to use Gradle profiler

    • -2
    • +3
    ./JavaConfigurationPerformanceTest.groovy
  1. … 19 more files in changeset.
Convert some easy classes to use Gradle profiler

    • -2
    • +2
    ./JavaConfigurationPerformanceTest.groovy
  1. … 19 more files in changeset.
Rename performance test infrastructure legacy classes

To make clear that they are using the Gradle build internal

infrastructure.

    • -2
    • +2
    ./JavaConfigurationPerformanceTest.groovy
  1. … 44 more files in changeset.
Rebaseline all performance test scenarios

There seems to be tiny gradual regression in performance, which causes unbearable

flakiness. Rebaselining all scenarios to catch future regressions.

    • -1
    • +1
    ./JavaConfigurationPerformanceTest.groovy
  1. … 30 more files in changeset.
Rebaseline some scenarios

We saw gradual regression in some of the scenarios. Rebaseling them.

    • -1
    • +1
    ./JavaConfigurationPerformanceTest.groovy
  1. … 3 more files in changeset.
Rebaseline some scenarios

We saw gradual regression in some of the scenarios. Rebaseling them.

    • -1
    • +1
    ./JavaConfigurationPerformanceTest.groovy
  1. … 3 more files in changeset.
Try latest nightly

    • -1
    • +1
    ./JavaConfigurationPerformanceTest.groovy
  1. … 35 more files in changeset.
Try latest nightly

    • -1
    • +1
    ./JavaConfigurationPerformanceTest.groovy
  1. … 35 more files in changeset.
Rebaseline `configure largeJavaMultiProject` performance test

As a 2-3% regression has been going on for some time now.

Signed-off-by: Rodrigo B. de Oliveira <rodrigo@gradle.com>

    • -1
    • +1
    ./JavaConfigurationPerformanceTest.groovy
Lock-in some performance improvements

    • -1
    • +1
    ./JavaConfigurationPerformanceTest.groovy
  1. … 31 more files in changeset.
Rebaseline JavaConfigurationPerformanceTest

    • -1
    • +1
    ./JavaConfigurationPerformanceTest.groovy
Recover

    • -2
    • +1
    ./JavaConfigurationPerformanceTest.groovy
  1. … 2 more files in changeset.
Change to processbuilder

    • -1
    • +2
    ./JavaConfigurationPerformanceTest.groovy
  1. … 1 more file in changeset.
Add warmup count for JavaConfigurationPerformanceTest

    • -0
    • +1
    ./JavaConfigurationPerformanceTest.groovy
Rebaseline configuration performance test

There was a small regression due to a correctness fix, which we

accept for 5.1. There already is a performance fix for it targeted

for 5.2. See #8103

    • -1
    • +1
    ./JavaConfigurationPerformanceTest.groovy
Rebaseline performance tests

    • -1
    • +1
    ./JavaConfigurationPerformanceTest.groovy
  1. … 30 more files in changeset.
Rebaseline to the same commit to the distribution commit

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

To account for minor regression due to detailed container

callback instrumentation. This information will help find

performance issues that are much bigger than the small overhead

the instrumentation adds.

    • -1
    • +1
    ./JavaConfigurationPerformanceTest.groovy
  1. … 31 more files in changeset.
Lock in recent performance improvements

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

We introduced a ThreadLocal in the project locking which slowed things

down a little bit (10s of ms) in several builds. Rebaselining to prevent

this from affecting all branches.

    • -1
    • +1
    ./JavaConfigurationPerformanceTest.groovy
  1. … 31 more files in changeset.
Rebaseline performance tests after merging single project lock changes

    • -1
    • +1
    ./JavaConfigurationPerformanceTest.groovy
  1. … 31 more files in changeset.
Unignore/rebaseline performance tests after kotlin-dsl-1.0-rc-11

Unignore/rebaseline those broken by the upgrade

Rebaseline those impacted ~2% by the extra EAP repo configuration

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -3
    • +3
    ./JavaConfigurationPerformanceTest.groovy
  1. … 2 more files in changeset.
Ignore failing perf tests temporarily

    • -2
    • +2
    ./JavaConfigurationPerformanceTest.groovy
  1. … 1 more file in changeset.
Rebaseline performance tests for Kotlin DSL 1.0-rc-10

Adding the kotlin-eap repo for Kotlin 1.3-RC affected performance.

Those tests should be rebaselined again when 1.3 final is used and the

extra repo configuration is removed.

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -1
    • +1
    ./JavaConfigurationPerformanceTest.groovy
  1. … 2 more files in changeset.
Rebaseline configure largeJavaMultiProject{KotlinDsl}

Both projects show some regressions. Rebaselining to unblock `master`

so we can investigate.

    • -1
    • +1
    ./JavaConfigurationPerformanceTest.groovy
Rebaseline performance tests

The introduction of the "platform" support introduced a couple small regressions,

but also improvements in some cases. This commit re-enables the Java IDE performance

test now that we have a baseline to compare with. Work on improving performance

is going to happen later.

    • -1
    • +1
    ./JavaConfigurationPerformanceTest.groovy
  1. … 31 more files in changeset.