Avoid unnecessary registry/plist reads (hundreds of them) by caching the brand code.

chrome/browser/search_engines/ui_thread_search_terms_data.cc

Index: chrome/browser/search_engines/ui_thread_search_terms_data.cc
diff --git a/chrome/browser/search_engines/ui_thread_search_terms_data.cc b/chrome/browser/search_engines/ui_thread_search_terms_data.cc
index 9a31685b52640c5fe56e2d0085624b76c859eb37..cdbb70f5945ded5551db2d4b2f25922c42ce2875 100644
--- a/chrome/browser/search_engines/ui_thread_search_terms_data.cc
+++ b/chrome/browser/search_engines/ui_thread_search_terms_data.cc
@@ -76,11 +76,14 @@ base::string16 UIThreadSearchTermsData::GetRlzParameterValue(
       BrowserThread::CurrentlyOn(BrowserThread::UI));
   base::string16 rlz_string;
 #if BUILDFLAG(ENABLE_RLZ)
+  static std::string* brand = NULL;

[grt (UTC plus 2), 2017/05/17 08:45:43]

the idiomatic way i've seen to do this sort of one-time initialization is:
  static std::string* brand = []() {
    auto brand = new std::string();
    if (!google_brand::GetBrand(brand))
      brand->clear();
    return brand;
  }();

[Boris Vidolov, 2017/05/17 18:37:10]

Sure. I've seen both and I just used the old-fashioned way (as here:
https://cs.chromium.org/chromium/src/url/gurl.cc?rcl=733abfce87eb65cf777c6c12...)

Changed now. Technically, I don't need to clear on failure based on the current
implementation of google_brand::GetBrand, but given that this is now a one-time
call, I will throw it there.

+  if (!brand) {
+    brand = new std::string();
+    google_brand::GetBrand(brand);
+  }
   // For organic brandcodes do not use rlz at all. Empty brandcode usually
   // means a chromium install. This is ok.
-  std::string brand;
-  if (google_brand::GetBrand(&brand) && !brand.empty() &&
-      !google_brand::IsOrganic(brand)) {
+  if (!brand->empty() && !google_brand::IsOrganic(*brand)) {
     // This call will return false the first time(s) it is called until the
     // value has been cached. This normally would mean that at most one omnibox
     // search might not send the RLZ data but this is not really a problem.