-
tim@chromium.org authored
Long term, we'd like to drop this further (i.e. 1 minute) and trust THROTTLED responses in the event of widespread backend outages. We'd like to run some stress tests of that infrastructure (at scale / under load), but in the meantime we want to address the problem for beta channel users / M22. We chose 5 minutes, which is a little more aggressive than the recommended value, but we believe is safe -- happy to discuss offline. This patch is very low risk (stability wise). although 5 minutes is a long time to wait for users who hit this due to transient failures. Current data suggests 500s occur around 0.02% of the time, and although backoff isn't limited to 500s it's unlikely to get hit frequently, and the user experience doesn't break down significantly. Effectiveness wise, We can run an experiment once it hits dev channel by returning 500s and watching for expected drops in QPS. BUG=139733,142029 Review URL: https://chromiumcodereview.appspot.com/10826194 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@151216 0039d316-1c4b-4281-b951-d872f2087c98
4494c5d6
