Show max latency on client's status bar

remoting/protocol/performance_tracker.cc

Index: remoting/protocol/performance_tracker.cc
diff --git a/remoting/protocol/performance_tracker.cc b/remoting/protocol/performance_tracker.cc
index c0372dd9a0e204db8d71b611b3e1386febea304b..c7b19bd8967c1ab353eb88dc7088ac438ab49a90 100644
--- a/remoting/protocol/performance_tracker.cc
+++ b/remoting/protocol/performance_tracker.cc
@@ -90,7 +90,8 @@ PerformanceTracker::PerformanceTracker()
       video_encode_ms_(kLatencySampleSize),
       video_decode_ms_(kLatencySampleSize),
       video_paint_ms_(kLatencySampleSize),
-      round_trip_ms_(kLatencySampleSize) {
+      round_trip_ms_(kLatencySampleSize),
+      max_round_trip_ms_(kLatencySampleSize) {
   uma_custom_counts_updater_ = base::Bind(&UpdateUmaCustomHistogramStub);
   uma_custom_times_updater_ = base::Bind(&UpdateUmaCustomHistogramStub);
   uma_enum_histogram_updater_ = base::Bind(&UpdateUmaEnumHistogramStub);
@@ -254,6 +255,7 @@ void PerformanceTracker::RecordRoundTripLatency(
       now - timestamps.latest_event_timestamp;
 
   round_trip_ms_.Record(round_trip_latency.InMilliseconds());
+  max_round_trip_ms_.Record(round_trip_latency.InMilliseconds());

[Sergey Ulanov, 2016/03/17 19:12:37]

If you use the same class for Average() and Max() then the same value will not
need to be recorded in two places, like this.

[Yuwei, 2016/03/17 20:24:44]

Acknowledged.

   uma_custom_times_updater_.Run(
       kRoundTripLatencyHistogram, round_trip_latency.InMilliseconds(),
       kLatencyHistogramMinMs, kLatencyHistogramMaxMs, kLatencyHistogramBuckets);