)
        when (os) {
            Os.WINDOWS -> {
                profilerParam("jprofiler")
                param("env.JPROFILER_HOME", "C:\\Program Files\\jprofiler\\jprofiler11.1.4")
            }

            else -> {
                profilerParam("async-profiler")
                param("env.FG_HOME_DIR", "/opt/FlameGraph")

) {
    LINUX(
        "Linux",
        androidHome = "/opt/android/sdk",
        jprofilerHome = "/opt/jprofiler/jprofiler11.1.4"
    ),
    WINDOWS(
        "Windows",
        androidHome = """C:\Program Files\android\sdk""",
        jprofilerHome = """C:\Program Files\jprofiler\jprofiler11.1.4""",
        perfTestWorkingDir = "P:/",
    ),
    MACOS(
        "Mac",
        androidHome = "/opt/android/sdk",

import org.gradle.profiler.BenchmarkResultCollector;
import org.gradle.profiler.BuildMutator;
import org.gradle.profiler.InvocationSettings;
import org.gradle.profiler.Profiler;
import org.gradle.profiler.ProfilerFactory;
import org.gradle.profiler.ScenarioDefinition;
import org.gradle.profiler.report.Format;
import org.gradle.profiler.result.BuildInvocationResult;

import java.io.File;

                val arch = if (os == Os.MACOS) Arch.AARCH64 else Arch.AMD64
                if (os == Os.WINDOWS) {
                    listOf("jprofiler")
                } else {
                    listOf("async-profiler", "async-profiler-heap")
                }.map { FlameGraphGenerationBuildSpec(scenario, os, arch, it) }
            }
        }

    inner
    class FlameGraphGenerationBuildSpec(

Use the https://github.com/gradle/gradle-profiler[Gradle Profiler] to find these kinds of bottlenecks.
With the Gradle Profiler, you can define scenarios like "Running 'assemble' after making an ABI-breaking change"
and run your build several times to collect profiling data.
Use the Profiler to produce build scans. Or combine it with method profilers like JProfiler and YourKit.
These profilers can help you find inefficient algorithms in custom plugins.

	return &cobra.Command{
		Use:   "diff <profile|file1.yaml> <profile|file2.yaml>",
		Short: "Diffs two Istio configuration profiles",
		Long:  "The diff subcommand displays the differences between two Istio configuration profiles.",
		Example: `  # Profile diff by providing yaml files
  istioctl profile diff manifests/profiles/default.yaml manifests/profiles/demo.yaml

  # Profile diff by providing a profile name
  istioctl profile diff default demo`,

    void testValidateUniqueProfileId() throws Exception {
        Settings settings = new Settings();
        Profile profile1 = new Profile();
        profile1.setId("test");
        settings.addProfile(profile1);
        Profile profile2 = new Profile();
        profile2.setId("test");
        settings.addProfile(profile2);

        SimpleProblemCollector problems = new SimpleProblemCollector();

    void testValidateUniqueProfileId() throws Exception {
        Settings settings = new Settings();
        Profile profile1 = new Profile();
        profile1.setId("test");
        settings.addProfile(profile1);
        Profile profile2 = new Profile();
        profile2.setId("test");
        settings.addProfile(profile2);

        SimpleProblemCollector problems = new SimpleProblemCollector();

        </plugins>
      </build>
    </profile>
    <profile>
      <id>profile4</id>
      <build>
        <plugins>
          <plugin>
            <groupId>org.apache.maven.its.plugins</groupId>
            <artifactId>maven-it-plugin-touch</artifactId>
            <version>2.1</version>
          </plugin>
        </plugins>
      </build>
    </profile>
  </profiles>

  xml.namespace="http://maven.apache.org/PROFILES/${version}"
  xml.schemaLocation="http://maven.apache.org/xsd/profiles-${version}.xsd">
  <id>profiles</id>
  <name>Profiles</name>
  <description><![CDATA[
    <b>Deprecated in Maven 2</b> Project-local overrides to the build process based on detected or user-provided environmental parameters.
    This is the model specification for <code>${basedir}/profiles.xml</code>.
  ]]></description>