---
title: "Compare profiles | Grafana documentation"
description: "Compare before and after profile costs and share Profiles Drilldown links with gcx."
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

# Compare profiles with `gcx`

You can compare profiles with `gcx`:

- Use `gcx profiles query` for one profile.
- Use `gcx profiles diff` for symbol costs across selectors, time windows, or both. `diff` uses [Pyroscope](https://grafana.com/docs/pyroscope/latest/)’s server-side comparison, not independently truncated top-function lists.

Follow these steps to compare profiles:

1. Configure a Grafana context with read access to Pyroscope.
2. Find the datasource UID with `gcx datasources list --type pyroscope`.
3. Find the profile type with `gcx profiles list-profile-types -d <datasource-uid>`.
4. Run then following commands to compare:

shell ![Copy code to clipboard](https://grafana.com/media/images/icons/icon-copy-small-2.svg) Copy

```shell
gcx profiles diff '{service_name="frontend",version="v1"}' '{service_name="frontend",version="v2"}' \
  -d <datasource-uid> --profile-type process_cpu:cpu:nanoseconds:cpu:nanoseconds \
  --before-from now-1h --before-to now \
  --after-from now-1h --after-to now --drilldown-link
```

In this example, both sides share a datasource and profile type. Repeat the same selector to compare different windows. Unsupported selectors warn and fall back without dropping scope.

**Use fixed timestamps for reproducible evidence**. All four bounds are required: RFC3339, Unix seconds, or relative times. They use one clock snapshot and resolve to whole seconds to match Drilldown.

Dedicated comparisons require the same exact `service_name`. Names requiring string escaping fall back to Explore, while other matchers are preserved separately.

For a profile UUID from exemplars, add `--profile-id <uuid> --drilldown-link` to `gcx profiles query`. A single ID opens the scoped flame graph and multiple IDs or stacktrace selectors fall back to Explore. Trace-ID-scoped queries suppress links because neither UI can preserve their scope.

## Interpret costs

Table-wide output shows the top 20 absolute self-cost changes.

JSON, YAML, and agents output retain all returned symbols, warnings, selections, units, and links. The backend node budget defaults to 50,000 in every format.

Take into account the following to interpret costs:

- Costs use the profile type’s raw sample unit.
- Recursive inclusive costs count only the outermost occurrence per stack.
- `self` attributes cost directly to a function.
- `total` includes callees.
- `delta` is after minus before, without duration or traffic normalization.
- Prefer comparable, equal-length windows: traffic, replicas, and sampling can change cost without a regression.
- `changePercent` is null for zero baselines or when either profile has no positive samples. Missing samples do not establish zero cost or improvement.
- `complete=false` means frames were folded into `other`; `omitted` reports their costs.
- Raise `--max-nodes` or narrow selectors to improve attribution.
- Absence from a pruned graph does not establish an added or removed function.

## Share evidence

To share evidence:

- `links.before` and `links.after` open individual profiles.
- `links.explore` opens before on the left and after on the right, with independent ranges.
- `links.comparison` opens the dedicated diff view when representable.

The following options are available:

- `--share-link` / `--open`: print or open split Explore.
- `--drilldown-link` / `--open-drilldown`: print or open Profiles Drilldown. You must enable Drilldown, since URLs target its Scenes contract used in version 3.1.0. Use Explore for older apps that don’t support that contract.