Getting the detailed V8 times comes at a measurable overhead, this piggybacking on the existing V8ExecuteMicroseconds data from the persistent V8SlowHistograms trial is most likely your best option here to limit negative side effects from multiple trials slowing down the user.
On Fri, 7 Jan 2022, 09:57 Leszek Swirski, <lesz...@chromium.org> wrote: > +Camillo Bruni <cbr...@google.com> > We have a V8.ExecuteMicroSeconds histogram which is enabled for 50% of > canary and dev (via the V8SlowHistograms > <https://source.chromium.org/chromium/chromium/src/+/main:gin/gin_features.cc;l=108;drc=26479386abe0c05c9661f6d8c1412dde636d8ecb> > feature > flag). Maybe you could somehow intercept writes to this histogram before > FCP? > > On Thu, Jan 6, 2022 at 2:35 PM Yuki Shiino <yukishi...@chromium.org> > wrote: > >> +v8-dev@googlegroups.com <v8-dev@googlegroups.com> >> >> >> 2022年1月5日(水) 9:05 Scott Violet <s...@google.com>: >> >>> Ping. Any suggestions? >>> >>> Thanks, >>> >>> -Scott >>> >>> On Tue, Dec 21, 2021 at 5:15 AM Yuki Shiino <yukishi...@chromium.org> >>> wrote: >>> >>>> +platform-architecture-dev <platform-architecture-...@chromium.org> >>>> >>>> 2021年12月21日(火) 9:45 Scott Violet <s...@google.com>: >>>> >>>>> Hello, >>>>> >>>>> I'm interested in tracking how much time we spend in v8 prior to fcp. >>>>> Any idea if we have a metric for this? Presumably such a metric would >>>>> involve instrumenting bindings, but I'm not positive there. >>>>> >>>> >>>> I know only about RuntimeCallStats >>>> <https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/platform/bindings/RuntimeCallStats.md> >>>> (V8 >>>> looks having the same concept maybe around here >>>> <https://source.chromium.org/chromium/chromium/src/+/main:v8/src/logging/runtime-call-stats.h;bpv=1;bpt=1;l=570?q=RuntimeCallStats%20case:yes&ss=chromium>). >>>> However, if you're interested in measuring it in the wild, RuntimeCallStats >>>> wouldn't be a good fit. >>>> >>>> Anyone else would know a better idea? >>>> >>>> Cheers, >>>> Yuki Shiino >>>> >>>> Thanks, >>>>> >>>>> -Scott >>>>> >>>> -- >> -- >> v8-dev mailing list >> v8-dev@googlegroups.com >> http://groups.google.com/group/v8-dev >> --- >> You received this message because you are subscribed to the Google Groups >> "v8-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to v8-dev+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/v8-dev/CAN0uC_TCyPxXdVGbAmh7JBR3e7UHxXYXtuW-yUpM9Q1hSbXBKQ%40mail.gmail.com >> <https://groups.google.com/d/msgid/v8-dev/CAN0uC_TCyPxXdVGbAmh7JBR3e7UHxXYXtuW-yUpM9Q1hSbXBKQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- -- v8-dev mailing list v8-dev@googlegroups.com http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/v8-dev/CAOeS1i-61rcY6XKwO_bJcbD-vEzD8McRYdvBYMExVqWX-C80CQ%40mail.gmail.com.
