Increase the UMA/UKM retry backoff levels to reduce server load on server issues.

This should change retries from

15s, 16.5s, ... 10min, 10min ..

to

5 minutes, 10 minutes, 20 minutes, ... 24h, 24h..


Bug: 873282
Change-Id: Ib1e3fdebdf155f171a51c73b29724f4ba4673c73
Reviewed-on: https://chromium-review.googlesource.com/1171512
Commit-Queue: Robert Kaplow (slow) <rkaplow@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582735}

components/metrics/metrics_upload_scheduler.cc

@@ -21,10 +21,10 @@ namespace {
 // longer before sending the next log. This backoff process helps reduce load
 // on a server that is having issues.
 // The following is the multiplier we use to expand that inter-log duration.
-const double kBackoffMultiplier = 1.1;
+const double kBackoffMultiplier = 2;
 
-// The maximum backoff interval in minutes.
-const int kMaxBackoffIntervalMinutes = 10;
+// The maximum backoff interval in hours.
+const int kMaxBackoffIntervalHours = 24;
 
 // Minutes to wait if we are unable to upload due to data usage cap.
 const int kOverDataUsageIntervalMinutes = 5;
@@ -37,7 +37,7 @@ base::TimeDelta BackOffUploadInterval(base::TimeDelta interval) {
       kBackoffMultiplier * interval.InMicroseconds()));
 
   base::TimeDelta max_interval =
-      base::TimeDelta::FromMinutes(kMaxBackoffIntervalMinutes);
+      base::TimeDelta::FromHours(kMaxBackoffIntervalHours);
   if (interval > max_interval || interval.InSeconds() < 0) {
     interval = max_interval;
   }
@@ -51,9 +51,9 @@ base::TimeDelta GetUnsentLogsInterval() {
   return base::TimeDelta::FromSeconds(3);
 }
 
-// Inital time delay after a log uploaded fails before retrying it.
+// Initial time delay after a log uploaded fails before retrying it.
 base::TimeDelta GetInitialBackoffInterval() {
-  return base::TimeDelta::FromSeconds(15);
+  return base::TimeDelta::FromMinutes(5);
 }
 
 }  // namespace