Open lmatz opened 9 months ago
Some notable phenomenon:
And why such an executor cache pattern?
4X:
1X:
4X:
1X:
Join Actor Input Blocking Time Ratio
and Join Actor Match Duration Per Second
are both about 4 times worse.4X:
1X:
AppendOnlyDedup
cannot keep up when scaling upHashJoin
generally keeps up when scaling up.Sort
operator does not keep up when scaling upProject
cannot keep up when scaling up (hard to believeThis issue has been open for 60 days with no activity. Could you please update the status? Feel free to continue discussion or close as not planned.
nightly-20240127
4X:
1X:
RW 4X: 1659K RW 1X: 592K (slower) 4X/1X Ratio: 2.8
Flink: http://metabase.risingwave-cloud.xyz/question/9549-nexmark-rw-vs-flink-avg-source-throughput-all-testbeds?rw_tag=nightly-20240127&flink_tag=v1.16.0&flink_label=flink-medium-1tm-test-20230104,flink-4x-medium-1tm-test-20240104&flink_metrics=avg-job-throughput-per-second
4X/1X Ratio: 3.16
RW:
Query Plan:
Dist Query Plan:
Flink:
Query Plan: