cc: Add UMA stats for record and raster time.

cc/resources/tile_manager.cc

 // Copyright 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "cc/resources/tile_manager.h"
 
 #include <algorithm>
 #include <limits>
 #include <string>
 
 #include "base/bind.h"
 #include "base/json/json_writer.h"
 #include "base/logging.h"
 #include "base/metrics/histogram.h"
+#include "base/metrics/histogram_macros.h"
+#include "base/timer/elapsed_timer.h"
 #include "base/trace_event/trace_event_argument.h"
 #include "cc/debug/devtools_instrumentation.h"
 #include "cc/debug/frame_viewer_instrumentation.h"
 #include "cc/debug/traced_value.h"
 #include "cc/layers/picture_layer_impl.h"
 #include "cc/resources/raster_buffer.h"
 #include "cc/resources/tile.h"
 #include "cc/resources/tile_task_runner.h"
 #include "ui/gfx/geometry/rect_conversions.h"
 
@@ skipping 76 matching lines @@
     UMA_HISTOGRAM_BOOLEAN("Renderer4.SolidColorTilesAnalyzed",
                           analysis_.is_solid_color);
 
     // Clear the flag if we're not using the estimator.
     analysis_.is_solid_color &= kUseColorEstimator;
   }
 
   void Raster(const RasterSource* raster_source) {
     frame_viewer_instrumentation::ScopedRasterTask raster_task(
         tile_id_, tile_resolution_, source_frame_number_, layer_id_);
+    base::ElapsedTimer timer;
 
     DCHECK(raster_source);
 
     raster_buffer_->Playback(raster_source_.get(), content_rect_,
                              contents_scale_);
+
+    base::TimeDelta elapsed = timer.Elapsed();
+    UMA_HISTOGRAM_COUNTS("Renderer4.RasterTaskUs", elapsed.InMicroseconds());

[enne (OOO), 2015/04/08 20:18:46]

This one seems like a pretty good regression metric, although it is definitely
prone to influence by outside changes, e.g. image decoding improvements.

I think if we ever start rastering from the display list directly, it might be
worth having a "null canvas" microbenchmark, where we don't do any of the work,
but just iterate through it as if we were doing the work.

[jbroman, 2015/04/08 20:37:42]

Agreed. I think the best we're hoping for is to have a signal if we suddenly
make things dramatically worse in the real world.
Might be an interesting microbenchmark, sure, but it seems orthogonal to this
bug, no?

[enne (OOO), 2015/04/08 21:03:49]

Yeah.  Just trying to think out loud about more targeted metrics that might
better track the real performance issues with less noise.

+    UMA_HISTOGRAM_COUNTS(
+        "Renderer4.RasterTaskPixelsPerMs",
+        content_rect_.size().GetArea() / elapsed.InMillisecondsF());
   }
 
   RasterSource::SolidColorAnalysis analysis_;
   scoped_refptr<RasterSource> raster_source_;
   gfx::Rect content_rect_;
   float contents_scale_;
   TileResolution tile_resolution_;
   int layer_id_;
   const void* tile_id_;
   int source_frame_number_;
@@ skipping 843 matching lines @@
   result -= other;
   return result;
 }
 
 bool TileManager::MemoryUsage::Exceeds(const MemoryUsage& limit) const {
   return memory_bytes_ > limit.memory_bytes_ ||
          resource_count_ > limit.resource_count_;
 }
 
 }  // namespace cc