[jira] [Commented] (JCLOUDS-1369) MultipartUploadSlicingAlgorithm makes suboptimal choices with few part sizes

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JCLOUDS-1369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319144#comment-16319144 ] 

ASF subversion and git services commented on JCLOUDS-1369:
----------------------------------------------------------

Commit 8cd68a35033312cd54822bc3f8e46ed629810712 in jclouds's branch refs/heads/master from [~gaul]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=8cd68a3 ]

JCLOUDS-1369: improving slicing with many parts

Previously with GCS and its maximum 32 parts, the slicing algorithm
would sliced 3.2 GB blobs into (31) 32 MB parts and (1) 2.3 GB part.
With this algorithm it creates (31) 100 MB parts and (1) smaller part.


> MultipartUploadSlicingAlgorithm makes suboptimal choices with few part sizes
> ----------------------------------------------------------------------------
>
>                 Key: JCLOUDS-1369
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1369
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-blobstore
>    Affects Versions: 2.0.3
>            Reporter: Andrew Gaul
>            Assignee: Andrew Gaul
>              Labels: google-cloud-storage
>
> When uploading a 3.2 GB blob to GCS I observed that MultipartUploadSlicingAlgorithm created (31) 32 MB parts and (1) 2.3 GB part.  Instead it should create (32) 100 MB parts which will increase bandwidth utilization and improve retries.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)