beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenneth Knowles (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (BEAM-38) Avoid repeated DoFn deserialization
Date Sat, 20 Feb 2016 02:53:18 GMT

     [ https://issues.apache.org/jira/browse/BEAM-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kenneth Knowles updated BEAM-38:
--------------------------------
    Description: Alluded to in our technical vision, we wish to remove at least some guarantees
about when a fresh DoFn instance is created. Repeated deserialization can become a major cost
when bundles are very small, as in some streaming pipelines.  (was: Alluded to in our technical
vision. Ignoring any tricks we might play to reuse a DoFn transparently, the model guarantees
a fresh instance for each bundle. This can become a major cost when bundles are very small,
as in some streaming pipelines.)

> Avoid repeated DoFn deserialization
> -----------------------------------
>
>                 Key: BEAM-38
>                 URL: https://issues.apache.org/jira/browse/BEAM-38
>             Project: Beam
>          Issue Type: New Feature
>          Components: beam-model
>            Reporter: Kenneth Knowles
>            Assignee: Frances Perry
>
> Alluded to in our technical vision, we wish to remove at least some guarantees about
when a fresh DoFn instance is created. Repeated deserialization can become a major cost when
bundles are very small, as in some streaming pipelines.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message