Throttling based on estimated completion time 3z6c31

[rasqual]

Let's say I'm in a location for 4 hours. I want to do an hour's worth of work with a , but I don't want to bog down the network needlessly by maxing out threads.

How about an option where I can specify how long I want the to last, as a target? Perhaps even specify a "at this time" option?

Taking the slightly simpler case, I'd click a spinner to change a time field which would result in "I'd like this to be ed in about 2 hours and 30 minutes." That would leave me with an hour to work on the file, and a half hour buffer. It would result in the least possible network utilization consistent with my needs.

Obviously this wouldn't be as deterministic as throttling by bandwidth, but this would be an extremely handy feature.

[rasqual]

bump.

[fdmrcfan]

I like this idea. I sometimes need to from private locations and this would make life easier. Now I stop all other s, set restrictions, and start for only the one site.

[Guest]

Right. The more I think about it, the more I'd like to see BOTH variations offered. Actually, a more full way of thinking about this is just a scheduling option, with several options (brackets represent controls where values may be updated; lowercase o is radio button)

Begin ing at [13][20] (this would default to the current time)
End :
o at [14][20] (this could default to something like an hour after current time)
o in [01][00] from now

The defaults could be intelligent, based on a quick partial of the file in question. That could also establish a "no less than" constraint on what a could enter.