[
https://issues.apache.org/jira/browse/BEAM-3617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16355611#comment-16355611
]
Kenneth Knowles commented on BEAM-3617:
---------------------------------------
I will take this one and track re-instating it. The priority is lower because
it has already served its purpose of forcing portability developments. But it
does still protect us from accidentally introducing hacks until all runners are
portable.
> Performance degradation on the direct runner
> --------------------------------------------
>
> Key: BEAM-3617
> URL: https://issues.apache.org/jira/browse/BEAM-3617
> Project: Beam
> Issue Type: Bug
> Components: runner-direct
> Reporter: Jean-Baptiste Onofré
> Assignee: Kenneth Knowles
> Priority: Blocker
> Fix For: 2.3.0
>
> Time Spent: 4h 40m
> Remaining Estimate: 0h
>
> Running Nexmark queries with the direct runner between Beam 2.2.0 and 2.3.0
> shows a performance degradation:
> {code}
> ========================================
> Beam 2.2.0 Beam 2.3.0
> Query Runtime(sec) Runtime(sec)
> ========================================
> 0000 6.4 10.6
> 0001 5.1 10.2
> 0002 3.0 5.8
> 0003 3.8 6.2
> 0004 0.9 1.4
> 0005 5.8 11.4
> 0006 0.8 1.4
> 0007 193.8 1249.1
> 0008 3.9 6.9
> 0009 0.9 1.3
> 0010 6.4 8.2
> 0011 5.0 9.4
> 0012 4.7 9.1
> {code}
> We can see especially Query 7 that is 10 times longer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
