mirror of
https://github.com/curl/curl.git
synced 2026-05-05 10:27:17 +03:00
620401f193
After Gmail called out the typo I fixed on
532d89a866, I've decided to paste the
whole man page into Google docs and check what other issues it would
spot.
I know, it sounds silly, but I've just spent the last hour and a half
going over each one of them and fixing everything which was a true
finding and non-controversial.
Closes #17480
37 lines
1.2 KiB
Markdown
37 lines
1.2 KiB
Markdown
---
|
|
c: Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
|
|
SPDX-License-Identifier: curl
|
|
Long: limit-rate
|
|
Arg: <speed>
|
|
Help: Limit transfer speed to RATE
|
|
Category: connection
|
|
Added: 7.10
|
|
Multi: single
|
|
See-also:
|
|
- rate
|
|
- speed-limit
|
|
- speed-time
|
|
Example:
|
|
- --limit-rate 100K $URL
|
|
- --limit-rate 1000 $URL
|
|
- --limit-rate 10M $URL
|
|
---
|
|
|
|
# `--limit-rate`
|
|
|
|
Specify the maximum transfer rate you want curl to use - for both downloads
|
|
and uploads. This feature is useful if you have a limited pipe and you would
|
|
like your transfer not to use your entire bandwidth. To make it slower than it
|
|
otherwise would be.
|
|
|
|
The given speed is measured in bytes/second, unless a suffix is appended.
|
|
Appending 'k' or 'K' counts the number as kilobytes, 'm' or 'M' makes it
|
|
megabytes, while 'g' or 'G' makes it gigabytes. The suffixes (k, M, G, T, P)
|
|
are 1024 based. For example 1k is 1024. Examples: 200K, 3m and 1G.
|
|
|
|
The rate limiting logic works on averaging the transfer speed to no more than
|
|
the set threshold over a period of multiple seconds.
|
|
|
|
If you also use the --speed-limit option, that option takes precedence and
|
|
might cripple the rate-limiting slightly, to help keep the speed-limit
|
|
logic working.
|