[Cyberduck-trac] [Cyberduck] #11000: Increase OneDrive multipart chunk size

Cyberduck trac at cyberduck.io
Tue Mar 24 00:50:59 UTC 2020

#11000: Increase OneDrive multipart chunk size
    Reporter:  Rjevski   |      Owner:
        Type:  defect    |     Status:  new
    Priority:  normal    |  Milestone:
   Component:  onedrive  |    Version:  7.2.5
    Severity:  normal    |   Keywords:
Architecture:  Intel     |   Platform:  macOS 10.14

 Just wondering if there are any plans to increase the OneDrive multipart
 chunk size?

 The official client syncs quite fast at around 17MB/s. Uploading the same
 file using Cyberduck hovers at around 6MB/s (with the change of the
 "factor" introduced recently as in https://github.com/iterate-
 ) - my current build (7.2.5) doesn't seem to have it implemented so I just
 simulated it by setting the "onedrive.upload.multipart.partsize.minimum"
 value to minimum*20.

 After setting the "minimum" part size setting to a ridiculously high value
 like 480000000 I am then able to get roughly the same speeds as the
 official client. This causes some weird behaviour with the transfer rate
 estimation and progress bar of Cyberduck as well as a "Java heap error"
 (probably out of memory?) when trying to upload a 1GB file. Reducing the
 value to half that (240000000) made the 1GB file upload fine and still had
 a speed comparable to the official client.

 Is there any chance we can up this value further, potentially depending on
 the file size? The official docs set an upper limit of 60MB per chunk:
 - with your experience interfacing with different cloud storage providers,
 is there any reason *not* to use the max chunk size a provider allows, and
 what determines an optimal chunk size?


Ticket URL: <https://trac.cyberduck.io/ticket/11000>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows

More information about the Cyberduck-trac mailing list