ProjectCreationPerformanceTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
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
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
    ./ProjectCreationPerformanceTest.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
    ./ProjectCreationPerformanceTest.groovy
  1. … 22 more files in changeset.
Optimize service registry performance

Our service registry infrastructure is far from being performant. Lookup by type is particularily expensive, and involves

looping through all supplied providers, and eventually go to the parent registries until we find a match, that we can cache.

This commit introduces a new method that allows a provider to tell if it is _candidate_ for providing a type (independently

of parameterized types), and introduces more caching of the result.

This improves performance of the service registry, at the cost of increased memory usage.

    • -1
    • +1
    ./ProjectCreationPerformanceTest.groovy
  1. … 7 more files in changeset.
Streamline naming of performance tests: core feature tests

    • -3
    • +1
    ./ProjectCreationPerformanceTest.groovy
  1. … 3 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
    • +38
    ./ProjectCreationPerformanceTest.groovy
  1. … 96 more files in changeset.