You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Hangxiang Yu (Jira)" <ji...@apache.org> on 2022/12/09 02:00:00 UTC
[jira] [Created] (FLINK-30345) Improve the serializer performace of state change of changelog
Hangxiang Yu created FLINK-30345:
------------------------------------
Summary: Improve the serializer performace of state change of changelog
Key: FLINK-30345
URL: https://issues.apache.org/jira/browse/FLINK-30345
Project: Flink
Issue Type: Improvement
Components: Runtime / State Backends
Reporter: Hangxiang Yu
Assignee: Hangxiang Yu
Fix For: 1.17.0, 1.16.1
Currently, AbstractStateChangeLogger use syncÂ
DataOutputViewStreamWrapper to serialize state change which is unnecessary because it will always be executed in single thread.
So replace it with a unsync one could improve the performance of serialization.
In my simple stateful WordCount case, it could improve TPS by 10% at least.
Furthermore, because the serialization and deserialization of key and value have been executed in some delegaed state backend, maybe we could avoid double serialization. It may improve the performance if the serialization logic is complex and even is the bottleneck.
This ticket focuses on the sync serializer problem.
The second problem about double serialization could also be disscussed, and I will create a new ticket if necessary.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)