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 2022/01/12 03:50:03 UTC

[jira] [Updated] (BEAM-6243) TFX pipelines experience a huge blowup in intermediate data size

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

Kenneth Knowles updated BEAM-6243:
----------------------------------

This Jira ticket has a pull request attached to it, but is still open. Did the pull request resolve the issue? If so, could you please mark it resolved? This will help the project have a clear view of its open issues.

> TFX pipelines experience a huge blowup in intermediate data size
> ----------------------------------------------------------------
>
>                 Key: BEAM-6243
>                 URL: https://issues.apache.org/jira/browse/BEAM-6243
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-flink
>            Reporter: Robert Bradshaw
>            Priority: P3
>          Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> The elements in TFX intermediate collections are dictionaries of (typically single-element) numpy arrays, which are (relatively) expensive to serialize (e.g. using pickle for the numpy wrapper of a primitive int/float, repeating the column names in every element).
> Though it'd be good to use a better intermediate representation, this is exacerbated because the fusion algorithm does not pack as much possible into executable stages. 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)