From abc089a33d947a398534163398e8ab634091686b Mon Sep 17 00:00:00 2001 From: Brian Hulette Date: Fri, 11 Feb 2022 12:44:10 -0800 Subject: [PATCH] Minor: Fix link to nexmark benchmarks (#16803) --- website/www/site/content/en/contribute/release-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/www/site/content/en/contribute/release-guide.md b/website/www/site/content/en/contribute/release-guide.md index bd93b1e3f0ec9..159741ad7957b 100644 --- a/website/www/site/content/en/contribute/release-guide.md +++ b/website/www/site/content/en/contribute/release-guide.md @@ -246,7 +246,7 @@ Measurements are available on [metrics.beam.apache.org](http://metrics.beam.apac All Runners which publish data should be checked for the following, in both *batch* and *streaming* mode: - [ParDo](http://metrics.beam.apache.org/d/MOi-kf3Zk/pardo-load-tests) and [GBK](http://metrics.beam.apache.org/d/UYZ-oJ3Zk/gbk-load-test): Runtime, latency, checkpoint duration -- [Nexmark](http://metrics.beam.apache.org/d/ahuaA_zGz/nexmark): Query runtime for all queries +- [Nexmark](http://metrics.beam.apache.org/d/ahudA_zGz/nexmark): Query runtime for all queries - [IO](http://metrics.beam.apache.org/d/bnlHKP3Wz/java-io-it-tests-dataflow): Runtime If regressions are found, the release branch can still be created, but the regressions should be investigated and fixed as part of the release process.