[Cyberduck-trac] [Cyberduck] #10278: Optimize Checksum Calculation

[Cyberduck]

#10278: Optimize Checksum Calculation
-------------------------+------------------------
 Reporter:  allklier     |         Owner:  dkocher
     Type:  enhancement  |        Status:  new
 Priority:  normal       |     Milestone:
Component:  s3           |       Version:  6.4.1
 Severity:  normal       |    Resolution:
 Keywords:               |  Architecture:
 Platform:  macOS 10.12  |
-------------------------+------------------------

Comment (by dkocher):

 Replying to [comment:2 jamshid]:
 > Agreed, it would be great if there was a way to disable the checksum
 because it takes too long on >100GB files. I notice people complain about
 it e.g. https://community.rackspace.com/general/f/general-discussion-
 forum/1775/cyberduck-incredibly-slow
 >
 > PS: (looking through some code changes I see you already know this) but
 although the ETag calculation is not officially defined by Amazon, the
 resulting ETag is a completed multipart upload is an MD5 of each part's
 MD5 followed by "-" and the number of parts. This could be verified if
 you're paranoid, though I guess it would have to be recomputed if
 Cyberduck is restarted in the middle of a multipart upload.
 We already do compute the returned concatenated MD5 hash for multipart
 uploads (see
 [https://trac.cyberduck.io/browser/trunk/s3/src/main/java/ch/cyberduck/core/s3/S3MultipartUploadService.java
 S3MultipartUploadService].

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