Increase Max Range for RasterPixelsPerMs

cc/base/histograms.h

Index: cc/base/histograms.h
diff --git a/cc/base/histograms.h b/cc/base/histograms.h
index a4c0c58cc90ee36dbe70605d6be194af06a2f7e8..77d71f63bc07f4c32c1ce875909e4a5dc80f4d77 100644
--- a/cc/base/histograms.h
+++ b/cc/base/histograms.h
@@ -64,8 +64,9 @@ const char* GetClientNameForMetrics();
       /* runtime constant. */                                               \
       UMA_HISTOGRAM_COUNTS(base::StringPrintf(time_histogram, client_name), \
                            time_sample);                                    \
-      UMA_HISTOGRAM_COUNTS(base::StringPrintf(area_histogram, client_name), \
-                           area_sample);                                    \
+      UMA_HISTOGRAM_CUSTOM_COUNTS(                                          \
+          base::StringPrintf(time_histogram, client_name), area_sample, 1,  \
+          100000000, 50);                                                   \

[ericrk, 2016/11/14 17:33:32]

isherman@ - when we update the range of an existing histogram, do we typically
rename (add 2, etc...) to prevent confusion? Or just add a note for the sheriff
when submitting?

[Ilya Sherman, 2016/11/14 17:57:32]

You should rename, yes.  Otherwise, the dashboard will show a confusing mix of
buckets under the same name.

     }                                                                       \
   }