Loop/Load Handling: Difference between revisions

'''October 13''' - While Firefox 34 is in Beta, we probably want to set the throttle to 100%, so that it is available to all beta users. Early beta of 33 had the feature active and in the default toolbar set, so we already have a good idea that we can handle the resulting load.

'''November 19''' - As we approach the uplift of 34 to release, we want to reduce the throttle to a lower value, around 10%. I propose that we do this several days out, to make sure we don't run into DNS caching issues.

'''November 19 - December 30''' - Gradually increase the throttle. 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. I would recommend giving at least 48 hours for the load to settle before adjusting 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.

'''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.

'''December 30 - February 15''' - Repeat the throttle increase process described above.  

'''February 15''' - {{Bug|1073218}} should land in Firefox 36, which will be in release around this date. We still want to give people time to upgrade before leaving users on 35 without a button in the default toolbar; one release cycle should be long enough.

'''March 30''' - Remove the throttle DNS record.