[Swift-devel] Is there a site count limit?

[Michael Wilde]

Ah, cool. Now that I see it again I remember why I didnt comment: its 
because it was complex and I didnt understand it.

I just spent a few minutes digesting the diagram, and yes, that gives a 
nice explanation of the top-level behavior.

I feel that the throttling mechanism is both important enough, timely 
(in that real users need it yet are stymied by it) complex enough, and 
interesting enough (ie it could merit a research paper) that we should 
dig back into it.

Add in coasters to the mix, and scheduling/throttling gets yet another 
dimension. (and both more complexity and an opportunity to reduce 
complexity based on knowledge of available workers).


On 4/15/09 11:19 AM, Ben Clifford wrote:
> On Wed, 15 Apr 2009, Michael Wilde wrote:
> 
>> Yes, this would be very good. And at the same time review the rest of the
>> throttle parameters. I always have to scratch my head and re-read the
>> descriptions to get the behavior I want. If the other throttles asre OK as-is,
>> then it would still be good to clarify their explanations in the properties
>> file test and provide examples in the user guide.
> 
> I drew a diagram and sent it to the swift-devel list that was a draft of a 
> graphical explanation of where the various throttle settings fit in. No 
> one commented so I have taken it no further.
> 
> http://mail.ci.uchicago.edu/pipermail/swift-devel/2009-February/004318.html
>