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 2020/08/10 17:07:22 UTC

[jira] [Commented] (BEAM-8474) A microbenchmark that exercises the FnAPI runner functionality

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

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

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.


> A microbenchmark that exercises the FnAPI runner functionality
> --------------------------------------------------------------
>
>                 Key: BEAM-8474
>                 URL: https://issues.apache.org/jira/browse/BEAM-8474
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-py-core
>            Reporter: Pablo Estrada
>            Priority: P2
>              Labels: stale-P2
>          Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> The main data paths for the Fn API runner are exercised by:
>  * Side inputs
>  * GBK
>  * State
>  * Timers
>  * SDF?
> A microbenchmark would have a number of stages that exercise one or more of these data paths.
> A microbenchmark suite may have more than one pipeline.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)