[jira] [Commented] (BEAM-13541) Use runtime information to improve CoGroupByKey caching

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-13541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17531863#comment-17531863 ] 

Beam JIRA Bot commented on BEAM-13541:
--------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> 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
>            Priority: P2
>              Labels: stale-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.7#820007)