[
https://issues.apache.org/jira/browse/BEAM-9822?focusedWorklogId=434674&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-434674
]
ASF GitHub Bot logged work on BEAM-9822:
----------------------------------------
Author: ASF GitHub Bot
Created on: 18/May/20 23:33
Start Date: 18/May/20 23:33
Worklog Time Spent: 10m
Work Description: nielm commented on pull request #11570:
URL: https://github.com/apache/beam/pull/11570#issuecomment-630488670
@allenpradeep
> 1. What mode should our import pipeline use? Should it use option b as
data in AVRO seems already sorted?
We can discuss this outside the scope of this PR.
> 2. Where should we document these modes of operation so that some customer
can use these?
I have added a section to the javadoc explaining these 3 modes of operation,
and their pros and cons.
----------------------------------------------------------------
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:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 434674)
Time Spent: 2h 20m (was: 2h 10m)
> SpannerIO: Reduce memory usage - especially when streaming
> ----------------------------------------------------------
>
> Key: BEAM-9822
> URL: https://issues.apache.org/jira/browse/BEAM-9822
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp
> Affects Versions: 2.20.0, 2.21.0
> Reporter: Niel Markwick
> Assignee: Niel Markwick
> Priority: P2
> Labels: google-cloud-spanner
> Fix For: 2.22.0
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> SpannerIO uses a lot of memory.
> In Streaming Dataflow, it uses many times as much (because dataflow creates
> many worker threads)
> Lower the memory use, and change default parameters during streaming to use
> smaller batches and disable grouping.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
