2performance

20GB file transfer

A transfer of about twenty gigabytes, where a dropped part is an expected event.

How it works

Use 100 MB parts, not 1 MB parts. One hundred megabyte parts stay inside store limits. Hash before you call it delivered.

A 20 GB master completes at 02:40 after part 140 retries. The morning review waits on the hash, not on the progress mail from 02:10.

Twenty gigabytes still fits an overnight home job. A coffee-shop up link will not finish it.

A USB copy with no hash can be short and still carry the right filename.

Keep the sending host awake or use resume.

The practical close is a log line: time, actor, byte count, result.
Without that line the transfer is a story.
With it, the next person can see whether this door did what the ticket claimed.
If the path is shared, say so in the partner profile so a later change does not silently pick a different limit, key, or region.
On a real ticket, write down the door, the byte count, and the clock.
For twenty gb file transfer, that means naming the host or bucket, the expected size, and the time the other side must have a complete file.
A progress bar is not that record.
A 200 response that arrives before the complete call is not that record.
If a retry is allowed, say how many and whether it resumes.
If a person must approve the send, name the person.
Partners who receive twenty gb file transfer files should match on hash or size before they import.
A same-length corrupt file passes a size check and fails a hash.
Keep the published hash off the only channel an attacker can edit, or treat it as a corruption check rather than a substitution check.
When the path changes, new key, new region, new cap, update the profile the same day so the next run does not use a stale limit.