You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2021/03/25 17:19:00 UTC
[jira] [Commented] (BEAM-11300) Optimize Nexmark pipelines
[ https://issues.apache.org/jira/browse/BEAM-11300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308842#comment-17308842 ]
Beam JIRA Bot commented on BEAM-11300:
--------------------------------------
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.
> 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: P2
> Labels: stale-P2
> 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.3.4#803005)