RichConsolePerformanceTest.groovy

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

  1. … 30 more files in changeset.
Rebaseline to the same commit to the distribution commit

  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. … 31 more files in changeset.
Lock in recent performance improvements

  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. … 31 more files in changeset.
Rebaseline performance tests after merging single project lock changes

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

To lock in memory usage improvements.

  1. … 32 more files in changeset.
Lock in some dependency management performance improvements

  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. … 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. … 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. … 31 more files in changeset.
  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.