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 2019/10/23 17:47:01 UTC

[jira] [Commented] (BEAM-8363) Nexmark regression in direct runner in streaming mode

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

Kenneth Knowles commented on BEAM-8363:
---------------------------------------

The direct runner does not actually have separate batch/streaming modes. So that toggle just changes how the Nexmark framework works.

> Nexmark regression in direct runner in streaming mode
> -----------------------------------------------------
>
>                 Key: BEAM-8363
>                 URL: https://issues.apache.org/jira/browse/BEAM-8363
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-direct
>    Affects Versions: 2.16.0
>            Reporter: Mark Liu
>            Priority: Critical
>             Fix For: 2.17.0
>
>         Attachments: regression_screenshot.png
>
>
> From Nexmark performance dashboard for direct runner: https://apache-beam-testing.appspot.com/explore?dashboard=5084698770407424, there is a regression for streaming mode happened on August 25.
> The runtime increased about 25% in two days.



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