v2.0.0-rt.3 tpch q3 perf degradation

[cyliu0]

Describe the bug

http://metabase.risingwave-cloud.xyz/question/26990-rw-avg-source-throughput-release?start_date=2024-03-01&testbed=medium-1cn-affinity&workload=tpch-q3

Error message/log

No response

To Reproduce

No response

Expected behavior

No response

How did you deploy RisingWave?

No response

The version of RisingWave

v2.0.0-rt.3

Additional context

No response

[fuyufjh]

Looks like an incidental jitter. As it doesn't block version releasing, we may run another time to see whether the issue recurs.

http://metabase.risingwave-cloud.xyz/question/4802-tpch-q3-bs-medium-1cn-affinity-avg-source-output-rows-per-second-rows-s-history-thtb-366?start_date=2023-07-01

[lmatz]

let's run it again: https://buildkite.com/risingwave-test/tpch-benchmark/builds/1132

[lmatz]

I suspect it is because kafka's ebs is different, let me run it again with the same configuration as the weekly test: https://buildkite.com/risingwave-test/tpch-benchmark/builds/1133

[lmatz]

after changing EBS to a better one, the performance is up. It's just a configuration issue.

I will change the configuration in the release testing pipeline