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:07 UTC
[jira] [Updated] (BEAM-8832) Slow GCS uploads for large Java staging jars
[ https://issues.apache.org/jira/browse/BEAM-8832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kenneth Knowles updated BEAM-8832:
----------------------------------
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.
> Slow GCS uploads for large Java staging jars
> --------------------------------------------
>
> Key: BEAM-8832
> URL: https://issues.apache.org/jira/browse/BEAM-8832
> Project: Beam
> Issue Type: Improvement
> Components: runner-dataflow
> Affects Versions: 2.16.0
> Reporter: Alan Myrvold
> Priority: P3
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> The default and max upload chunk size is 1M, in
> [https://github.com/apache/beam/blob/master/runners/google-cloud-dataflow-java/src/main/java/org/apache/beam/runners/dataflow/util/GcsStager.java#L96]
> This should be at least 8M to improve performance.
> 8m is the default python write chunk size
> [https://github.com/apache/beam/blob/master/sdks/python/apache_beam/io/gcp/gcsio.py#L86]
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)