/prombench v3.2.1

⏱️ Welcome to Prometheus Benchmarking Tool. ⏱️

Compared versions: PR-16327 and v3.2.1

After the successful deployment (check status here), the benchmarking results can be viewed at:

• Prometheus Meta
• Prombench Dashboard
• Grafana Explorer, Loki logs
• Parca profiles (e.g. in-use memory)

Available Commands:

• To restart benchmark: /prombench restart v3.2.1
• To stop benchmark: /prombench cancel
• To print help: /prombench help

/prombench cancel

the pipeline is stuck

well, the PR misses commits now.

We had a partial merge in here: the target branch was updated with the commits but this PR is still open.
Github folks will help synchronize this.

Can you share the status of 3.3.0? I see that rc.1 was created but the benchmarking was canceled?

rc1 was released last week https://github.com/prometheus/prometheus/releases/tag/v3.3.0-rc.1

I see that, thanks. I'm curious about the rc.1 benchmarks and promotion or if there are known issues that are being resolved before an rc.2.

https://github.com/prometheus/prometheus/blob/main/RELEASE.md#release-shepherd-responsibilities

With the pre-release, the release shepherd is responsible for running and monitoring a benchmark run of the pre-release for 3 days, after which, if successful, the pre-release is promoted to a stable release.

From what I can tell the benchmarking was canceled, maybe I'm missing something. Thanks for your time.

a benchmark was run for >1d for rc0 #16194 and there are no differences between rc0 and rc1 thus I only ran the rc1 for some hours.

But let's do it by the book, opened #16434 for that 3 days benchmark.

I'll publish 3.3.0 after that.

Thanks for paying attention to that.

/prombench cancel