Concurrent transfer

How it works

Concurrency fills a link and can starve voice or hit a session cap. A scheduler decides how many. Uncontrolled concurrency is how a morning pile-on starts.

Three editors each upload 8 GB at 09:00 on a 100 Mbps up link. Each gets about 30 Mbps and all finish around 36 minutes. Uncapped against a partner who allows two sessions, the third fails immediately.

How it differs

Concurrent transfers are multiple files. Parallel transfer can mean multiple streams of one file.

A success metric per transfer hides that together they blew a quota.

Count bytes across the set.

On the ticket

• 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 concurrent 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 concurrent 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.