[
https://issues.apache.org/jira/browse/FLINK-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot closed FLINK-7799.
---------------------------------
Resolution: Auto Closed
This issue was labeled "stale-minor" 7 ago and has not received any updates so
I have gone ahead and closed it. If you are still affected by this or would
like to raise the priority of this ticket please re-open, removing the label
"auto-closed" and raise the ticket priority accordingly.
> Improve performance of windowed joins
> -------------------------------------
>
> Key: FLINK-7799
> URL: https://issues.apache.org/jira/browse/FLINK-7799
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Legacy Planner
> Affects Versions: 1.4.0
> Reporter: Fabian Hueske
> Assignee: Xingcan Cui
> Priority: Minor
> Labels: auto-closed, stale-assigned
>
> The performance of windowed joins can be improved by changing the state
> access patterns.
> Right now, rows are inserted into a MapState with their timestamp as key.
> Since we use a time resolution of 1ms, this means that the full key space of
> the state must be iterated and many map entries must be accessed when joining
> or evicting rows.
> A better strategy would be to block the time into larger intervals and
> register the rows in their respective interval. Another benefit would be that
> we can directly access the state entries because we know exactly which
> timestamps to look up. Hence, we can limit the state access to the relevant
> section during joining and state eviction.
> The good size for intervals needs to be identified and might depend on the
> size of the window.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
