Skip to content
Weaver Docs

Bandwidth

Two kinds of control shape how much Weaver pulls. A speed limit caps the rate. Download quotas and per-server quotas cap bytes per window. Schedules can change both on a clock.

Speed Limit

Section titled “Speed Limit”

The global speed limit is a rate ceiling for all downloads. Set it from the queue header for an immediate change, or in Settings → General → Speed Limit with Apply Now and Reset to Unlimited. WEAVER_MAX_DOWNLOAD_SPEED seeds it on first start.

Each server can carry its own limit under Servers, and each egress can carry one under Advanced Networking. A download runs at the lowest of the global, egress, and server limits that apply to it.

Download Quotas

Section titled “Download Quotas”

For a metered connection, give the egress your downloads leave through a download quota. The System egress covers a plain connection; a VPN or proxy egress covers only what goes out that way. A quota has a window of one block, daily, weekly, or monthly, an allowance in bytes, and a reset time. When it is spent, downloads stop using that egress until the window resets. Set TZ in Docker so windows match your billing cycle.

The ISP bandwidth cap from earlier releases became the System egress’s download quota on upgrade, with the bytes already counted carried over. Setting up quotas, what happens when one is reached, and where usage shows are covered in Advanced Networking.

Per-server quotas are the same idea scoped to one provider. Use a download quota for your connection and server quotas for block accounts.

On A Schedule

Section titled “On A Schedule”

Schedule rules can set the global, egress, and server speed limits, and turn quota metering on or off. See Scheduling.

Section titled “Related”