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/12 03:51:03 UTC

[jira] [Updated] (BEAM-11300) Optimize Nexmark pipelines

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

Kenneth Knowles updated BEAM-11300:
-----------------------------------

This Jira ticket has a pull request attached to it, but is still open. Did the pull request resolve the issue? If so, could you please mark it resolved? This will help the project have a clear view of its open issues.

> Optimize Nexmark pipelines
> --------------------------
>
>                 Key: BEAM-11300
>                 URL: https://issues.apache.org/jira/browse/BEAM-11300
>             Project: Beam
>          Issue Type: Bug
>          Components: testing-nexmark
>            Reporter: Sam Whittle
>            Priority: P3
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Several of the nexmark queries can be improved to have better performance:
> - Query3 uses stateful processing and a CogroupByKey which introduces an unnecessary shuffle compared to just using stateful processing.  Additionally BagState is more appropriate to use than ValueState<List<>>
> - Query5 uses a binary combiner when a custom combiner is more appropriate
> - Query10 has excessive logging



--
This message was sent by Atlassian Jira
(v8.20.1#820001)