You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yanfei Lei (Jira)" <ji...@apache.org> on 2024/04/07 01:59:00 UTC
[jira] [Assigned] (FLINK-34973) FLIP-425: Asynchronous Execution Model
[ https://issues.apache.org/jira/browse/FLINK-34973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yanfei Lei reassigned FLINK-34973:
----------------------------------
Assignee: Yanfei Lei
> FLIP-425: Asynchronous Execution Model
> --------------------------------------
>
> Key: FLINK-34973
> URL: https://issues.apache.org/jira/browse/FLINK-34973
> Project: Flink
> Issue Type: New Feature
> Components: Runtime / Checkpointing, Runtime / State Backends, Runtime / Task
> Reporter: Zakelly Lan
> Assignee: Yanfei Lei
> Priority: Major
> Fix For: 2.0.0
>
>
> This is a sub-FLIP for the disaggregated state management and its related work, please read the FLIP-423 first to know the whole story.
> FLIP-424 introduces asynchronous state APIs with callbacks allowing state access to be executed in threads separate from the task thread, making better usage of I/O bandwidth and enhancing throughput. This FLIP proposes an execution framework for asynchronous state APIs. The execution code path for the new API is completely independent from the original one, where many runtime components are redesigned. We intend to delve into the challenges associated with asynchronous execution and provide an in-depth design analysis for each module. Furthermore, we will conduct a performance analysis of the new framework relative to the current implementation and examine how it measures up against other potential alternatives.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)