PER_DAY(
        displayName = "Slow Performance Regression Test",
        timeout = 420,
        channel = "commits",
    ),
    PER_WEEK(
        displayName = "Performance Experiment",
        timeout = 420,
        channel = "experiments",
    ),
    FLAKINESS_DETECTION(
        displayName = "Performance Test Flakiness Detection",
        timeout = 600,
        defaultBaselines = "flakiness-detection-commit",

     * determined experimentally to match our desired probability of false positives.
     */
    // NB: yes, this is surprisingly high, but that's what the experiments said was necessary
    // Raising this number slows the worst-case contains behavior, speeds up hashFloodingDetected,
    // and reduces the false-positive probability.
    static final int MAX_RUN_MULTIPLIER = 13;

			return i
		}
		i++
		fails++
		if fails >= 4+i>>4 && i < t {
			// Give up on IndexByte, it isn't skipping ahead
			// far enough to be better than Rabin-Karp.
			// Experiments (using IndexPeriodic) suggest
			// the cutover is about 16 byte skips.
			// TODO: if large prefixes of sep are matching
			// we should cutover at even larger average skips,

*.eu-south-1.airflow.amazonaws.com
*.eu-south-2.airflow.amazonaws.com
*.eu-west-1.airflow.amazonaws.com
*.eu-west-2.airflow.amazonaws.com
*.eu-west-3.airflow.amazonaws.com
*.ewp.live
*.ex.futurecms.at
*.ex.ortsinfo.at
*.experiments.sagemaker.aws
*.firenet.ch
*.fk
*.frusky.de
*.futurecms.at
*.gateway.dev
*.hosted.app
*.hosting.myjino.ru
*.hosting.ovh.net
*.id.pub
*.il-central-1.airflow.amazonaws.com
*.in.futurecms.at
*.jm

  /**
   * A map of contents pre-created before experiment starts to only measure map creation cost. The
   * implementation for the creation of contents is independent and could be different from that of
   * the map under test.
   */
  Map<Element, Element> contents;

  /** Map pre-created before experiment starts to only measure iteration cost during experiment. */
  Map<Element, Element> map;

## Quick Start

{
  "performanceTests" : [ {
    "testId" : "org.gradle.performance.experiment.declarativedsl.DeclarativeDslConfigurationPerformanceTest.configure",
    "groups" : [ {
      "testProject" : "largeEmptyMultiProjectDeclarativeDsl",
      "coverage" : {
        "per_commit" : [ "linux", "macOs", "windows" ]
      }
    } ]
  }, {
    "testId" : "org.gradle.performance.experiment.declarativedsl.DeclarativeDslFirstUsePerformanceTest.clean checkout",

*.eu-south-1.airflow.amazonaws.com
*.eu-south-2.airflow.amazonaws.com
*.eu-west-1.airflow.amazonaws.com
*.eu-west-2.airflow.amazonaws.com
*.eu-west-3.airflow.amazonaws.com
*.ewp.live
*.ex.futurecms.at
*.ex.ortsinfo.at
*.experiments.sagemaker.aws
*.firenet.ch
*.fk
*.frusky.de
*.futurecms.at
*.gateway.dev
*.hosted.app
*.hosting.myjino.ru
*.hosting.ovh.net
*.id.pub
*.il-central-1.airflow.amazonaws.com
*.in.futurecms.at
*.jm

[ {
  "scenario" : "org.gradle.performance.experiment.declarativedsl.DeclarativeDslFirstUsePerformanceTest.clean checkout",
  "durations" : [ {
    "testProject" : "largeEmptyMultiProjectDeclarativeDsl",
    "linux" : 450
  } ]
}, {
  "scenario" : "org.gradle.performance.experiment.declarativedsl.DeclarativeDslFirstUsePerformanceTest.cold daemon",
  "durations" : [ {
    "testProject" : "largeEmptyMultiProjectDeclarativeDsl",
    "linux" : 422
  } ]

### Configuration cache enabled by default

The build of Gradle enables the configuration cache by default as a dogfooding experiment.

Most tasks that are used to build Gradle support the configuration cache, but some don't. For example, building the documentation currently requires you to disable the configuration cache.