Chromium Code Reviews| Index: chrome/browser/history/in_memory_database.cc |
| =================================================================== |
| --- chrome/browser/history/in_memory_database.cc (revision 106923) |
| +++ chrome/browser/history/in_memory_database.cc (working copy) |
| @@ -10,6 +10,7 @@ |
| #include "base/time.h" |
| #include "base/utf_string_conversions.h" |
| #include "build/build_config.h" |
| +#include "chrome/browser/history/history_field_trial.h" |
| namespace history { |
| @@ -91,8 +92,9 @@ |
| // just not exist yet. |
| } |
| base::TimeTicks end_load = base::TimeTicks::Now(); |
| - UMA_HISTOGRAM_MEDIUM_TIMES("History.InMemoryDBPopulate", |
| - end_load - begin_load); |
| + UMA_HISTOGRAM_MEDIUM_TIMES( |
| + "History.InMemoryDBPopulate" + HistoryFieldTrial::GetGroupSuffix(), |
|
jar (doing other things)
2011/10/24 18:40:55
There is a nicer(?) or at least common patterns fo
brettw
2011/10/25 01:55:02
I guess that sounds worse to my thinking. Wouldn't
Scott Hess - ex-Googler
2011/10/26 21:44:59
Can you have it both ways? Old histogram for non-
jar (doing other things)
2011/10/27 00:23:55
The usual pattern is to keep the old histogram unc
|
| + end_load - begin_load); |
| UMA_HISTOGRAM_COUNTS("History.InMemoryDBItemCount", db_.GetLastChangeCount()); |
| { |