SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Overload Design Team Status

aliya avatar
aliya
13 diapositives · 260 Views · Aug 20, 2014

The Cisco Design Team, formed in January 2007, focuses on simulations of overload mechanisms. Composed of experts, including many non-IETF participants, the team holds bi-weekly calls to discuss progress. They have agreed on a simulation model and developed several independent simulators to determine baseline behaviors during overload scenarios. Preliminary results indicate the impact of stateless versus stateful 503 responses on system performance. The team's next steps include comparing algorithms from various sources and preparing a proposal for Philadelphia.

#overload design team status #overload design team status ppt #powerpoint #presentation
Overload Design Team Status - slide 1
01 / 13Overload Design Team Status
1 / 17

Télécharger la présentation

Overload Design Team Status
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. Overload Design Team Status Jonathan Rosenberg Cisco

  2. Team Overview • Design team formed January 2007 • Working on simulations of overload mechanisms • Composed of experts in this area • Many non-IETF participants • Bi-Weekly Calls

  3. Current Status • Agreed on simulation model • Several indpendendent simulators developed • Simulations performed to determine baseline behavior • Drop requests on overload, no 503 [sim1] • Send 503 on overload, no retry [sim2] • Retry on 503 [sim3]

  4. Baseline Results (Volker)

  5. Baseline Results (Shen)

  6. Stateful vs. Stateless 503 • Found that stateless 503 server transactions seriously worsen performance • Team agreed to use stateless 503 model despite this because faster 503 processing is critical overall

  7. Nortel Algorithm • Use 503/Retry-After and turn off traffic to server during interval • Retry-After value determined algorithmically from queue sizes • Equals amount of time for queue to drain to low watermark

  8. Results

  9. AT&T Algorithm • During each Measurement Interval, Core Proxy estimates: • Mean processing rate mt, • Queue length at end of measurement interval qt, • Core Proxy calculates the retry after period as the time needed for Core Proxy to process the queued messages that exceed the target queueing delay: Retry-after-delay = qt/mt - a x de • Retry-after-delay updated each Control Interval anddistributed to Edge Proxies in 503 responses,

  10. Results

  11. Columbia Algorithm • Sending elements send their current load forward • Receiving elements send back desired load • Receiving elements can compute fair share bandwidth allocations and fine grained load adjustment • No simulation results yet

  12. Bell Labs Algorithm • Overload Control Feedback Loop in SIP • SIP extension that realizes an overload control feedback loop to upstream neighbors. • Transport vehicle for feedback generated by an overload control algorithm. • Orthogonal to the specific control algorithm used. • draft-hilt-sipping-overload-03.txt • Overload Control Algorithm • Algorithm that determines fine grained load feedback to adjust incoming load. • No simulation results yet.

  13. Next Steps • Waiting for folks to finish implementing their algorithms • Once done, can do the real work of comparing results and doing additional simulations • Targeting proposal for Philadelphia