AbstractTaskOutputCacheJavaPerformanceTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
More rebaselining of performance tests

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

    • -1
    • +1
    ./AbstractTaskOutputCacheJavaPerformanceTest.groovy
  1. … 11 more files in changeset.
Add performance tests for caching native

    • -62
    • +0
    ./AbstractTaskOutputCacheJavaPerformanceTest.groovy
  1. … 6 more files in changeset.
Create build options only once

They are effectively immutable constants, so no need to

create them again and again in sevaral different places.

    • -2
    • +2
    ./AbstractTaskOutputCacheJavaPerformanceTest.groovy
  1. … 29 more files in changeset.
Rebaseline caching performance tests on 4.2.1

4.2.1 has faster unpacking for the build cache.

    • -1
    • +1
    ./AbstractTaskOutputCacheJavaPerformanceTest.groovy
Represent Gradle properties and corresponding command line option as data structure (#2784)

    • -2
    • +2
    ./AbstractTaskOutputCacheJavaPerformanceTest.groovy
  1. … 48 more files in changeset.
Rebaseline task output caching performance tests

We had some improvements (and some smaller regressions) which we want

to lock in now.

    • -1
    • +1
    ./AbstractTaskOutputCacheJavaPerformanceTest.groovy
Use our own hashing architecture, take 2 (#2817)

This replaces Guava's hashing. We need this for two reasons:

- it allows the addition of custom hash functions, like BLAKE2b which would not be possible with Guava's closed design

- it fixes a few performance issues that Guava only fixes in version 20 (which we can't upgrade to right now, because we still need to support Java 5 in places)

    • -1
    • +1
    ./AbstractTaskOutputCacheJavaPerformanceTest.groovy
  1. … 159 more files in changeset.
Use snapshots while packing task outputs (#2756)

We've already collected snapshots after the task, so no need to walk the file system again.

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

    • -1
    • +1
    ./AbstractTaskOutputCacheJavaPerformanceTest.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
    ./AbstractTaskOutputCacheJavaPerformanceTest.groovy
  1. … 22 more files in changeset.
Rebaseline task output caching test

    • -1
    • +1
    ./AbstractTaskOutputCacheJavaPerformanceTest.groovy
  1. … 1 more file in changeset.
Explicit clean up before performance test measurements (#2640)

Previously we were using a workaround where odd runs were removed from measurements, and executed a `clean` build instead of the measured build.

Performance tests can now specify `cleanTasks`, similar to how they specify `tasksToRun`. These `cleanTasks` will be executed before each run (warm-up and measurement runs alike).

A new column is added to performance test tables to track this new information. It is a nullable column to allow for test results added by older versions of Gradle.

I've updated the task output caching tests and the Maven vs. Gradle comparisons to declare `cleanTasks` instead of the old hack with the odd-even runs.

    • -11
    • +3
    ./AbstractTaskOutputCacheJavaPerformanceTest.groovy
  1. … 27 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
    • +1
    ./AbstractTaskOutputCacheJavaPerformanceTest.groovy
  1. … 23 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
    • +1
    ./AbstractTaskOutputCacheJavaPerformanceTest.groovy
  1. … 22 more files in changeset.
Remove deprecated task caching system properties

+review REVIEW-6503

    • -3
    • +2
    ./AbstractTaskOutputCacheJavaPerformanceTest.groovy
  1. … 13 more files in changeset.
Streamline naming of performance tests: build cache tests

    • -2
    • +2
    ./AbstractTaskOutputCacheJavaPerformanceTest.groovy
  1. … 2 more files in changeset.
Added minimumVersion for historical performance tests

    • -0
    • +1
    ./AbstractTaskOutputCacheJavaPerformanceTest.groovy
  1. … 5 more files in changeset.
Cleanup Java performance test projects and scenarios

- Sort tests into packages

- Add new test projects: `largeMonolithicJavaProject`,

`largeJavaMultiProject`, `mediumJavaMultiProjectWithTestNG`

- Cleanup template.gradle file

-- Remove "old Java" templates

-- Remove unused Scala and Groovy performance

test project configurations

-- Remove large enterprise performance test projects

- Simplify Java scenarios: clean assemble, first use, change test,

getting IDE models, dependency report, abi change, non-abi change

- Adjust tests to not use old test projects anymore

- Add file mutators

    • -0
    • +70
    ./AbstractTaskOutputCacheJavaPerformanceTest.groovy
  1. … 96 more files in changeset.
Initial version of simplified test project generator

Dependencies between sources and projects are still missing.

    • -2
    • +2
    ./AbstractTaskOutputCacheJavaPerformanceTest.groovy
  1. … 21 more files in changeset.