You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Piotr Nowojski (Jira)" <ji...@apache.org> on 2019/09/19 10:14:00 UTC

[jira] [Assigned] (FLINK-14044) Reducing synchronization in AsyncWaitOperator

     [ https://issues.apache.org/jira/browse/FLINK-14044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Piotr Nowojski reassigned FLINK-14044:
--------------------------------------

    Assignee: Arvid Heise

> Reducing synchronization in AsyncWaitOperator
> ---------------------------------------------
>
>                 Key: FLINK-14044
>                 URL: https://issues.apache.org/jira/browse/FLINK-14044
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Task
>            Reporter: Arvid Heise
>            Assignee: Arvid Heise
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently, AsyncWaitOperator receives computed results from a user thread and puts it in {{StreamElementQueue}}. This queue is synchronized as the emitter thread pulls available elements in a blocking fashion. With the recent migration to mailbox model, these elements are then put into a letter to be outputted in the mailbox thread.
> If we directly send the results from the user thread to the mailbox, we can get rid of any synchronization as everything happens in the user thread. That will slim down the code heavily.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)