|
|
Created:
4 years, 2 months ago by dougarnett Modified:
4 years, 1 month ago CC:
chromium-reviews, romax+watch_chromium.org, fgorski+watch_chromium.org, dewittj+watch_chromium.org, petewil+watch_chromium.org, chili+watch_chromium.org, asvitkine+watch_chromium.org, dimich+watch_chromium.org Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
Description[OfflinePages] Adds TimeToStart UMA for background load requests.
BUG=656099
Committed: https://crrev.com/d3b9a8de5aca133c4b7cbdf2edf254cd3f8702a5
Cr-Commit-Position: refs/heads/master@{#427186}
Patch Set 1 #
Total comments: 4
Patch Set 2 : Using factory instead of macro for dynamic histogram name #Patch Set 3 : Inlined histogram constants #
Total comments: 3
Messages
Total messages: 33 (17 generated)
The CQ bit was checked by dougarnett@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
dougarnett@chromium.org changed reviewers: + dimich@chromium.org, petewil@chromium.org
Redo on the TimeToStart UMA with milliseconds instead of seconds and so using time delta macro.
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
lgtm
dougarnett@chromium.org changed reviewers: + holte@chromium.org
lgtm
https://chromiumcodereview.appspot.com/2440733002/diff/1/components/offline_p... File components/offline_pages/background/request_coordinator.cc (right): https://chromiumcodereview.appspot.com/2440733002/diff/1/components/offline_p... components/offline_pages/background/request_coordinator.cc:87: base::TimeDelta::FromSeconds(kMaxDurationSeconds), kDurationBuckets); You don't want this bound to change even if you change this constant for some other reason (it will make buckets incompatible between new and old versions of chrome), so it would be better to just inline the value here.
https://chromiumcodereview.appspot.com/2440733002/diff/1/components/offline_p... File components/offline_pages/background/request_coordinator.cc (right): https://chromiumcodereview.appspot.com/2440733002/diff/1/components/offline_p... components/offline_pages/background/request_coordinator.cc:84: UMA_HISTOGRAM_CUSTOM_TIMES( Also you shouldn't use this macro with a computed histogram name, since it uses a static pointer to the histogram. Instead, use base::Histogram::FactoryTimeGet() (or split this into seperate macro invokations for each histogram name)
The CQ bit was checked by dougarnett@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was checked by dougarnett@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
https://codereview.chromium.org/2440733002/diff/1/components/offline_pages/ba... File components/offline_pages/background/request_coordinator.cc (right): https://codereview.chromium.org/2440733002/diff/1/components/offline_pages/ba... components/offline_pages/background/request_coordinator.cc:84: UMA_HISTOGRAM_CUSTOM_TIMES( On 2016/10/20 20:51:11, Steven Holte wrote: > Also you shouldn't use this macro with a computed histogram name, since it uses > a static pointer to the histogram. Instead, use > base::Histogram::FactoryTimeGet() (or split this into seperate macro invokations > for each histogram name) Done. Thanks https://codereview.chromium.org/2440733002/diff/1/components/offline_pages/ba... components/offline_pages/background/request_coordinator.cc:87: base::TimeDelta::FromSeconds(kMaxDurationSeconds), kDurationBuckets); On 2016/10/20 20:46:31, Steven Holte wrote: > You don't want this bound to change even if you change this constant for some > other reason (it will make buckets incompatible between new and old versions of > chrome), so it would be better to just inline the value here. Done.
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
https://codereview.chromium.org/2440733002/diff/40001/components/offline_page... File components/offline_pages/background/request_coordinator.cc (right): https://codereview.chromium.org/2440733002/diff/40001/components/offline_page... components/offline_pages/background/request_coordinator.cc:88: base::TimeDelta::FromMilliseconds(100), base::TimeDelta::FromDays(7), 50, This will have second bucket that would take everything from 100ms to >3hrs. And 50 is a good number of buckets already. Would log scale help here? I think we want more resolution in the first couple hours and then less resolution...
https://codereview.chromium.org/2440733002/diff/40001/components/offline_page... File components/offline_pages/background/request_coordinator.cc (right): https://codereview.chromium.org/2440733002/diff/40001/components/offline_page... components/offline_pages/background/request_coordinator.cc:88: base::TimeDelta::FromMilliseconds(100), base::TimeDelta::FromDays(7), 50, On 2016/10/21 18:30:25, Dmitry Titov wrote: > This will have second bucket that would take everything from 100ms to >3hrs. And > 50 is a good number of buckets already. Would log scale help here? I think we > want more resolution in the first couple hours and then less resolution... I thought this one would give exponential buckets vs. using LinearHistogram::FactoryTimeGet. I will double check the reference I used.
https://codereview.chromium.org/2440733002/diff/40001/components/offline_page... File components/offline_pages/background/request_coordinator.cc (right): https://codereview.chromium.org/2440733002/diff/40001/components/offline_page... components/offline_pages/background/request_coordinator.cc:88: base::TimeDelta::FromMilliseconds(100), base::TimeDelta::FromDays(7), 50, On 2016/10/21 23:16:38, dougarnett wrote: > On 2016/10/21 18:30:25, Dmitry Titov wrote: > > This will have second bucket that would take everything from 100ms to >3hrs. > And > > 50 is a good number of buckets already. Would log scale help here? I think we > > want more resolution in the first couple hours and then less resolution... > > I thought this one would give exponential buckets vs. using > LinearHistogram::FactoryTimeGet. I will double check the reference I used. Code doc here: https://cs.chromium.org/chromium/src/base/metrics/histogram_macros.h?rcl=0&l=136 OfflinePages.SavePageTime uses this and is not linear. I can certainly drop the max though.
Thanks for explanation! LGTM
The CQ bit was checked by dougarnett@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from petewil@chromium.org, holte@chromium.org Link to the patchset: https://codereview.chromium.org/2440733002/#ps40001 (title: "Inlined histogram constants")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_arm64_dbg_recipe on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/android_arm6...)
The CQ bit was checked by dougarnett@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Committed patchset #3 (id:40001)
Message was sent while issue was closed.
Description was changed from ========== [OfflinePages] Adds TimeToStart UMA for background load requests. BUG=656099 ========== to ========== [OfflinePages] Adds TimeToStart UMA for background load requests. BUG=656099 Committed: https://crrev.com/d3b9a8de5aca133c4b7cbdf2edf254cd3f8702a5 Cr-Commit-Position: refs/heads/master@{#427186} ==========
Message was sent while issue was closed.
Patchset 3 (id:??) landed as https://crrev.com/d3b9a8de5aca133c4b7cbdf2edf254cd3f8702a5 Cr-Commit-Position: refs/heads/master@{#427186} |