You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/01/11 17:11:00 UTC
[jira] [Commented] (BEAM-13541) Use runtime information to improve CoGroupByKey caching
[ https://issues.apache.org/jira/browse/BEAM-13541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472943#comment-17472943 ]
Kenneth Knowles commented on BEAM-13541:
----------------------------------------
Seems like per https://beam.apache.org/contribute/jira-priorities/ this is a P2 improvement.
> Use runtime information to improve CoGroupByKey caching
> -------------------------------------------------------
>
> Key: BEAM-13541
> URL: https://issues.apache.org/jira/browse/BEAM-13541
> Project: Beam
> Issue Type: Improvement
> Components: sdk-ideas
> Reporter: Sunil Pedapudi
> Assignee: Robert Bradshaw
> Priority: P2
> Fix For: 2.36.0
>
> Time Spent: 6.5h
> Remaining Estimate: 0h
>
> Currently, CoGroupByKey creates UnionTables that are Flattened. The Flattened output is processed by a GroupByKey to produce a CoGbkResult (via ConstructCoGbkResultFn).
>
> Given the performance of CoGBK is greatly impacted based on the which elements are cached in the (finitely sized) in-memory results, it would be useful if CoGbkResult can use runtime information to prioritize which elements are stored in-memory.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)