Seed throttle about mapproxy HOT 4 OPEN

req/sec and kb/sec would be tricky to implement in combination with --concurrency, because the seeders run in separate processes and can't share a single progress meter.
A delay should be easier to implement.

from mapproxy.

Delay between requests should be fine.

from mapproxy.

This seems to be very important for us, because we need to seed source, that warns against sanction in cases of overuse (which is not defined precisely).

from mapproxy.

please provide a feature to set the minimum delay when the mapproxy-seed failed to fetch. by default it set as 2 seconds with the same incremental delays.

it's good we can set base minimum greater than 2 seconds and its incremental delays more than 2 seconds. let's say 10 second for the base minimum and 15-20 seconds for its incremental.
apply logaritmic incremental also beneficial.

from mapproxy.