Add several new TRACE call and UMA metrics for SetupProfile().
I've replaced measuring GetProfile() (which includes cached profiles) with SetupProfile() which is more useful to track. I've added metrics to track the expensive components under SetupProfile(), which are -chrome::RegisterProfilePrefs -chrome_prefs::CreateProfilePrefs -ProfileImpl::OnPrefsLoaded. There currently are UMA histograms called Startup.SlowStartupPreferenceLoading, but I'm setting up different versions of these. They are tracking almost but not exactly the same things, but the current ones are only triggered for slow startups. I considered modifying these to add a control version, but I thought adding new ones was better because: -The histograms I'm adding have better names since they are called what they are actually checking -I'm measuring at what I think is a better place (inside the method itself instead of near the caller. -The new histograms are easily comparable for the work I'm doing since they are for all data (can just check percentile data). Also changed the TRACE argument from path.value().c_str() to path.MaybeAsASCII() since the former was only giving the address inside the trace (I'm guessing it never worked). If someone wants to have themselves also be added as an owner to any of the new histograms let me know. BUG=454789 Review URL: https://codereview.chromium.org/937713003 Cr-Commit-Position: refs/heads/master@{#317078}
Showing
Please register or sign in to comment