performance

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Rebase performance tests with 5.7-20190722220035+0000 baseline

#10348 might have an influence on the performance of these scenarios.

  1. … 11 more files in changeset.
Rebaseline to lock performance improvements

Temporarily use 5.6 as the baseline for Santa Tracker `assembleDebug` case.

This was scenario made faster when transform nodes for external files were accidentally not scheduled, at the cost of making the clean cache case much slower. These nodes are now scheduled again, making this scenario slower. Use 5.6 as the baseline to ensure this doesn't become worse than 5.6.

Temporarily use 5.6 as the baseline for Santa Tracker `assembleDebug` case.

This was scenario made faster when transform nodes for external files were accidentally not scheduled, at the cost of making the clean cache case much slower. These nodes are now scheduled again, making this scenario slower. Use 5.6 as the baseline to ensure this doesn't become worse than 5.6.

Temporarily use 5.6 as the baseline for Santa Tracker `assembleDebug` case.

This was scenario made faster when transform nodes for external files were accidentally not scheduled, at the cost of making the clean cache case much slower. These nodes are now scheduled again, making this scenario slower. Use 5.6 as the baseline to ensure this doesn't become worse than 5.6.

Rebaseline JavaConfigurationPerformanceTest

Remove GFileUtils.cleanDirectory()

  1. … 6 more files in changeset.
Fix version string

Rebaseline JavaIDEModelPerformanceTest

Both `get IDE model on largeJavaMultiProject for {IDEA,Eclipse}` seem

to have regressed by about 2-3%.

See gradle/gradle-private#2584

Rebaseline clean assembleDebug on santaTrackerAndroidBuild with clean transforms cache

Seems like a regression happened between 5.7-20190806220042+0000 and

5.7-20190807220120+0000.

See #10255

Rebase ExcludeRuleMergingPerformanceTest

There seems to be a tiny regression that now pushed this over the

edge sporadically. Possibly related to the rebase in 949aa2c.

Fix santaTrackerAndroid on release

By resetting it to a state where it works with

the baseline.

Rebase new performance test as consequence of #10191 and #10192

Merge pull request #10244 from gradle/wolfs/more-profiler-tests

Convert some easy classes to use Gradle profiler

Move Gradle options to args

Tasks should only contain actual tasks.

Rebaseline to mitigate impacts of flakiness

Rebaseline SwiftBuildPerformanceTest.incremental compile on bigSwiftApp

Looking at the history, there's a gradual tiny regression. Rebaseline it.

Convert JavaFirstUsePerformanceTest to use Gradle profiler

  1. … 1 more file in changeset.
Convert JavaFirstUsePerformanceTest to use Gradle profiler

  1. … 1 more file in changeset.
Convert JavaFirstUsePerformanceTest to use Gradle profiler

  1. … 1 more file in changeset.
Convert JavaFirstUsePerformanceTest to use Gradle profiler

  1. … 1 more file in changeset.
Fix failed historical performance test (#10173)

There're 4 failed historical performance tests.

Two of them are because previously `enableFeaturePreview` was not correctly configured for old Gradle build. This PR fixes them with Gradle version check.

Two of them are because of [this change](https://github.com/gradle/performance-comparisons/commit/c640ae2e31e8c8657e6654791ff02ba26ac95304) using a Gradle 4.6+ API.

  1. … 1 more file in changeset.
Remove newlines added by IDEA

Convert some easy classes to use Gradle profiler

  1. … 4 more files in changeset.
Convert some easy classes to use Gradle profiler

  1. … 5 more files in changeset.
Convert some easy classes to use Gradle profiler

  1. … 5 more files in changeset.
Convert some easy classes to use Gradle profiler

  1. … 5 more files in changeset.
Set min version for Groovy performance test

Set min version for Groovy performance test

Set min version for Groovy performance test