[
https://issues.apache.org/jira/browse/FLINK-32444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17782658#comment-17782658
]
Piotr Nowojski commented on FLINK-32444:
----------------------------------------
{quote}
Does it give us a performance benefits?
{quote}
Yes. One one job that I've looked into recently, a subtask reading from Kafka,
filtering/projecting records and doing local windowed aggregation, with object
reused disabled, is spending something between 25%-50% time inside
{{CopyingChainingOutput}}.
If there are no correctness issues with built-in operators/functions in Flink
SQL I would be also giving big +1 for enabling reuse by default.
> Enable object reuse for Flink SQL jobs by default
> -------------------------------------------------
>
> Key: FLINK-32444
> URL: https://issues.apache.org/jira/browse/FLINK-32444
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / API
> Reporter: Jark Wu
> Priority: Major
> Fix For: 1.19.0
>
>
> Currently, object reuse is not enabled by default for Flink Streaming Jobs,
> but is enabled by default for Flink Batch jobs. That is not consistent for
> stream-batch unification. Besides, SQL operators are safe to enable object
> reuse and this is a great performance improvement for SQL jobs.
> We should also be careful with the Table-DataStream conversion case
> (StreamTableEnvironment) which is not safe to enable object reuse by default.
> Maybe we can just enable it for SQL Client/Gateway and TableEnvironment.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
