[
https://issues.apache.org/jira/browse/FLINK-25318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461164#comment-17461164
]
Xintong Song commented on FLINK-25318:
--------------------------------------
I think [~pnowojski] has raised a very important point.
Currently, we have been relying on ByteDance & Alibaba internal benchmark
setups for performance analysis. In order for the wide community get involved
(at least being cautious not to break things), we certainly need a unified &
public visible benchmark setup, either the micro benchmarks or something else.
I've created a subtask FLINK-25356 to track this effort.
> Improvement of scheduler and execution for Flink OLAP
> -----------------------------------------------------
>
> Key: FLINK-25318
> URL: https://issues.apache.org/jira/browse/FLINK-25318
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination, Runtime / Network
> Affects Versions: 1.14.0, 1.12.5, 1.13.3
> Reporter: Shammon
> Priority: Major
> Labels: Umbrella
> Fix For: 1.15.0
>
>
> We use flink to perform OLAP queries. We launch flink session cluster, submit
> batch jobs to the cluster as OLAP queries, and fetch the jobs' results. OLAP
> jobs are generally small queries which will finish at the seconds or
> milliseconds, and users always submit multiple jobs to the session cluster
> concurrently. We found the qps and latency of jobs will be greatly affected
> when there're tens jobs are running, even when there's little data in each
> query. We will give the result of benchmark for the latest version later.
> After discussed with [~xtsong], and thanks for his advice, we create this
> issue to trace and manager Flink OLAP related improvements. More users and
> developers are welcome and feel free to create Flink OLAP related subtasks
> here, thanks
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
