You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Danny McCormick (Jira)" <ji...@apache.org> on 2022/06/05 01:15:00 UTC

[jira] [Commented] (BEAM-14464) Optimize precombining table.

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

Danny McCormick commented on BEAM-14464:
----------------------------------------

This issue has been migrated to https://github.com/apache/beam/issues/21675

> Optimize precombining table.
> ----------------------------
>
>                 Key: BEAM-14464
>                 URL: https://issues.apache.org/jira/browse/BEAM-14464
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-core
>            Reporter: Robert Bradshaw
>            Priority: P2
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> The current code constructs, hashes, and compares full WindowedValues for the grouping key, which ends up dominating the time spent in the combining table when using trivial combiners (like Sum.integers()). We only need compare the (structural value of the) key and windows, and can emit the windows in the global case.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)