Confirmed users
632
edits
Loop/Load Handling: Difference between revisions
Jump to navigation
Jump to search
→Recommended Handling
(→Recommended Handling: Added list of servers of interest) |
|||
| Line 71: | Line 71: | ||
=== Recommended Handling === | === Recommended Handling === | ||
'''Week of October 13''' - While Firefox 34 is in Beta, we want to test the throttle's proper functioning, while not leaving the feature disabled for many users for a long time. 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 load of setting the throttle to 100%. To that end, we should set the throttle to 10% on initial release, and then increase it every second business day. My proposal is to increase by doubling every second day until we reach 100%; that is: 10% on day 1, 20% on day 3, 40% on day 5 | '''Week of October 13''' - While Firefox 34 is in Beta, we want to test the throttle's proper functioning, while not leaving the feature disabled for many users for a long time. 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 load of setting the throttle to 100%. To that end, we should set the throttle to 10% on initial release, and then increase it every second business day. My proposal is to increase by doubling every second day until we reach 100%; that is: 10% on day 1, 20% on day 3 ({{Bug|1087397}}), 40% on day 5 ({{Bug|1087610}}), and 100% on day 7 ({{Bug|1087616}}). | ||
'''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%. 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%. I propose that we do this several days out, to make sure we don't run into DNS caching issues. | ||