Confirmed users
632
edits
Loop/Load Handling: Difference between revisions
→Recommended Handling
| Line 75: | Line 75: | ||
'''Week of November 19''' - As we approach the uplift of 34 to release, we want to reduce the throttle to a lower value, around 10% ({{Bug|1103028}}). I propose that we do this several days out, to make sure we don't run into DNS caching issues. | '''Week of November 19''' - As we approach the uplift of 34 to release, we want to reduce the throttle to a lower value, around 10% ({{Bug|1103028}}). I propose that we do this several days out, to make sure we don't run into DNS caching issues. | ||
'''Approximately November 19 - December 30''' - Gradually increase the throttle (20% on Dec 8: {{Bug|1108745}}; 40% on Dec 10: {{Bug|1109777}}; 80% on Dec 17: {{Bug|1112820}}). Observe server load and behavior (Loop server, Simple Push server, and TokBox infrastructure). As we are convinced the servers are equipped to handle the load, we increase the throttle according to how much headroom we believe the servers have. On any given increase, I would not recommend increasing the load by more than a factor of 2. I would recommend giving at least 48 hours for the load to settle before any subsequent adjustments to the throttle value. During this time period, release users will gain access to the feature, and beta users will have the button appear in their default toolbar. | '''Approximately November 19 - December 30''' - Gradually increase the throttle (20% on Dec 8: {{Bug|1108745}}; 40% on Dec 10: {{Bug|1109777}}; 80% on Dec 17: {{Bug|1112820}}; 100% on Dec 19: {{Bug|1113838}}). Observe server load and behavior (Loop server, Simple Push server, and TokBox infrastructure). As we are convinced the servers are equipped to handle the load, we increase the throttle according to how much headroom we believe the servers have. On any given increase, I would not recommend increasing the load by more than a factor of 2. I would recommend giving at least 48 hours for the load to settle before any subsequent adjustments to the throttle value. During this time period, release users will gain access to the feature, and beta users will have the button appear in their default toolbar. | ||
'''Week of December 30''' - Leading up to the uplift of 35 to release, we again reduce the throttle to 10%. Note that the throttle acts as a ratchet: once active, the service remains active. Reducing the throttle will not cause the feature to disappear from 34 browsers. | '''Week of December 30''' - Leading up to the uplift of 35 to release, we again reduce the throttle to 10%. Note that the throttle acts as a ratchet: once active, the service remains active. Reducing the throttle will not cause the feature to disappear from 34 browsers. | ||