Re: [Sipping] Re: draft-rosenberg-sipping-overload-reqs recovery

Hi, Jonathan,

From: "Jonathan Rosenberg" <jdrosen@cisco.com>
>
> Cullen Jennings wrote:
>
>>
>> A possible additional requirement....
>>
>> Imagine a system (perhaps a single proxy) that could do 100cps. It is  in 
>> steady state doing 80cps with very few retransmission. Then for 5 
>> minutes the incoming requests goes to 500cps then drops back to an 
>> incoming call rate of 80cps. The question is, how long before the  system 
>> gets back to the state where it if is successfully processing  all the 
>> 80cps?
>
> As soon as it can. Are you suggesting a requirement here? Seems like this 
> is an implementation thing and wouldn't impact any protocol mechanisms.
>
>>
>> I have seen systems that never recover - that is bad. I think one of  the 
>> design goals is that it is at least possible to build to systems  that 
>> recover back to steady state relatively quickly after an  overload 
>> impulse.
>
> Sure; but I'm not sure I see the protocol requirement.

I may have read too much into Cullen's note, but what *I* thought was being 
discussed was a "net" incoming rate of 500 cps, and what I thought Cullen 
was saying was that when the "net" incoming rate drops back to 80 cps, the 
system should not continue to present a "gross" (new requests + 
retransmitted requests) incoming rate of 500 cps for a very long time.

That seemed more of a protocol requirement than just saying "please don't 
fall over and not get up".

Thanks,

Spencer 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP