[
https://issues.apache.org/jira/browse/BEAM-11629?focusedWorklogId=554541&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-554541
]
ASF GitHub Bot logged work on BEAM-11629:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 19/Feb/21 01:00
Start Date: 19/Feb/21 01:00
Worklog Time Spent: 10m
Work Description: robertwb edited a comment on pull request #13739:
URL: https://github.com/apache/beam/pull/13739#issuecomment-781739778
The windowing information should be about 10 bytes/record overhead (most of
that for the 64-bit timestamp), so something odd is going on here. I do think
we need to save this information, as there's no telling if the next step (which
has not been built yet) will inspect this metadata.
What are the actual elements that are getting encoded? (And what Coder is
being used?)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 554541)
Time Spent: 3h 10m (was: 3h)
> Optimize the cache storage for InteractiveRunner
> ------------------------------------------------
>
> Key: BEAM-11629
> URL: https://issues.apache.org/jira/browse/BEAM-11629
> Project: Beam
> Issue Type: Improvement
> Components: runner-py-interactive
> Reporter: Dmytro Kozhevin
> Assignee: Dmytro Kozhevin
> Priority: P2
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> Currently InteractiveRunner wraps every record of the cached PCollection into
> WindowedValue. There is 2 problems about this:
> 1) The windowing information is unnecessary for the batch-mode runs
> (everything is in the same global window).
> 2) Since the cache is stored as text, we pickle the WindowedValue, which adds
> ~500 bytes of data to every record (e.g. a cache of just 1000000 integers
> would take ~500MB instead of ~4MB).
> These issues significantly slow down the interactive runs for data with lots
> of small rows.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
