# Install gradle-profiler with Homebrew

Profiling and benchmarking tool for Gradle builds. Version 0.25.2 via Homebrew; verified 2026-07-11.

## Install

```sh
sudo av install brew:gradle-profiler
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install gradle-profiler
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:gradle-profiler
- **Package manager:** Homebrew
- **Version:** 0.25.2
- **Source summary:** Profiling and benchmarking tool for Gradle builds
- **Homepage:** <https://github.com/gradle/gradle-profiler/>
- **Repository:** <https://github.com/gradle/gradle-profiler>
- **Last updated:** 2026-07-11T11:51:29Z
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- gradle-profiler (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 0.25.2
## Project history and usage

Gradle Profiler is a Gradle organization tool for repeatedly running builds and collecting benchmarking or profiling data. Its history is best understood as part of the Gradle performance culture rather than as a broad standalone ecosystem.

### Project history

The official README describes Gradle Profiler as a tool that automates gathering profiling and benchmarking information for Gradle builds. It integrates with build scans, Async Profiler, JProfiler, YourKit, Java Flight Recorder, HPROF heap dumps, Chrome Trace output, and build-operation timing.

The project lives under the Gradle GitHub organization and is distributed through release binaries as well as package managers such as Homebrew and SDKMAN. Its 0.x versioning reflects a focused engineering utility rather than a large end-user platform.

### Adoption history

Adoption is concentrated among build engineers, Android teams, Gradle plugin authors, and maintainers who need repeatable before-and-after measurements for Gradle version upgrades or build-logic changes. The README's scenario-file support shows the intended workflow: encode a build scenario, run warmups and iterations, then compare outputs.

### How it is used

Typical usage is `gradle-profiler --benchmark --project-dir <build> <task>` for timing comparisons, or `gradle-profiler --profile <profiler> --project-dir <build> <task>` for deeper profiling. Scenario files in HOCON format support groups, Gradle versions, tasks, daemon modes, mutations, build operation measurements, and IDE sync scenarios.

The tool produces benchmark HTML/CSV output and profile artifacts under `profile-out` by default. It can also compare multiple Gradle versions, which makes it useful when a package-manager upgrade changes build behavior.

### Why package nerds care

Gradle Profiler matters to package nerds because it is the small tool used to decide whether bigger build-tool package changes helped or hurt. It makes Gradle upgrades, Java runtime choices, daemon settings, and cache behavior measurable instead of anecdotal.

The Homebrew package is convenient because performance checks often happen on developer workstations before CI jobs or release engineering pipelines adopt a new Gradle line.

### Timeline

- 0.x line: Gradle Profiler releases are published from the Gradle GitHub repository.
- 0.23.0: The README identifies this as the last version for builds that require Gradle 5.x support.
- 0.24.0: The release notes describe Java 17 as the runtime requirement and Gradle 6.0 as the minimum supported Gradle version.

### Related projects

- Gradle Build Tool is the target build system measured by Gradle Profiler.
- Develocity and Gradle Build Scan are related analysis surfaces for build performance.
- Async Profiler, Java Flight Recorder, JProfiler, YourKit, Chrome Trace, and Perfetto are profiling or visualization tools used by Gradle Profiler.

### Sources

- <https://github.com/gradle/gradle-profiler>
- <https://github.com/gradle/gradle-profiler/releases>
- <https://raw.githubusercontent.com/gradle/gradle-profiler/master/README.md>


## Security Notes

narrow executable package without higher-risk signals.

- **Geiger risk:** green / low
- narrow executable package without higher-risk signals


## Combined YAML source

View the package source record on GitHub. [combined/gradle-profiler.yml](https://github.com/mxcl/pkgdb/blob/main/combined/gradle-profiler.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph