Bandwidth scheduling

How it works

The scheduler starts jobs at 01:00 or caps them until 18:00. The path stays usable by day. A window shorter than the transfer fails every night. Size the window from measured throughput.

A 30 GB push is scheduled 01:00 to 05:00 on a 40 Mbps night cap. It needs about 100 minutes and fits. A new 80 GB file does not. They split the file or widen the window before the first miss.

How it differs

Scheduling is not throttling. One picks the clock. The other picks the rate. Use both.

A window in local time breaks when clocks change.

State the zone.

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 bandwidth scheduling, 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 bandwidth scheduling 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.