[
https://issues.apache.org/jira/browse/BEAM-4750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16732383#comment-16732383
]
Kenneth Knowles commented on BEAM-4750:
---------------------------------------
This has been carried from version to version with no action. It seems clear
that InMemoryStateInternals is used by a lot more than the direct runner, so it
is not OK to introduce perf regressions just for the direct runner.
> Beam performance degraded significantly since 2.4
> -------------------------------------------------
>
> Key: BEAM-4750
> URL: https://issues.apache.org/jira/browse/BEAM-4750
> Project: Beam
> Issue Type: Bug
> Components: runner-core
> Affects Versions: 2.4.0, 2.5.0
> Reporter: Vojtech Janota
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 2.10.0
>
>
> Starting from Beam 2.4 onwards the *InMemoryStateInternals* class in the
> *beam-runners-core-java* module does an expensive Coder encode/decode
> operation when copying object state. This has significant impact on
> performance and pipelines that previously took low minutes do not finish
> within hours in our case. Based on the discussion on the dev mailing list,
> the main motivation for this change was to enforce Coder sanity, something
> that should arguably remain within the realm of the DirectRunner and should
> not leak into the core layer.
> Links to commits that introduced the new behaviour:
> * [https://github.com/apache/beam/commit/32a427c]
> * [https://github.com/apache/beam/commit/8151d82]
>
> Additional details and surrounding discussion can be found here:
> *
> https://lists.apache.org/thread.html/1e329318a4dafe27b9ff304d9460d05d8966e5ceebaf4ebfb948e2b8@%3Cdev.beam.apache.org%3E
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
