W3C home > Mailing lists > Public > public-web-perf@w3.org > March 2017

Re: Minutes [was: Re: [3/1/17] webperf group call @ 10AM PST]

From: Ilya Grigorik <igrigorik@google.com>
Date: Tue, 7 Mar 2017 23:04:40 +1100
Message-ID: <CADXXVKokreW8H9w6ehrnVJjc41nk8rviWFo8B_qUxGWe2jX6pw@mail.gmail.com>
To: Shubhie Panicker <panicker@google.com>
Cc: Xiaoqian Wu <xiaoqian@w3.org>, public-web-perf <public-web-perf@w3.org>
That comment was referring to the open PR on the spec. Todd suggested we
wait for Chrome implementation to roll out and gauge if it causes any
breakage/feedback, and then decide on whether we ought to land this or not.

On Tue, Mar 7, 2017 at 2:34 PM, Shubhie Panicker <panicker@google.com>
wrote:

>
>
> On Thu, Mar 2, 2017 at 8:16 AM, Xiaoqian Wu <xiaoqian@w3.org> wrote:
>
>> Hi,
>>
>> The minutes of this week's webperf group call are available:
>> https://www.w3.org/2017/03/01-webperf-minutes.html
>>
>> Next call will be 3/22/2017.
>>
>> Plain text version:
>> ==============
>>
>> Using User Timing at scale
>>
>> Dan: working on React.. CDT integration was great
>> … there is no way for a library to tell if user is recording or not,
>> we're afraid of wasting memory
>> … we're calling clearmarks/measures all the time, but it means we can't
>> harvest it later
>> … our main target is CDT
>> … i.e. in dev mode
>> an example -> https://‌facebook.github.io/‌react/‌docs/‌optimizing-perf
>> ormance.html#profiling-components-with-chrome-timeline
>> a) sounds like there is a need for API in devtools for in "record mode"
>> b) you should log some data to performance timeline.. perhaps with
>> lower fidelity
>> Nic: we monitor React today, we look at routechange events
>> Dan: we expose UT for every component in dev mode
>> Beacon: Enforce payload limits via Fetch API
>>
>> Enforce payload limits via Fetch API: https://‌github.com
>> /‌w3c/‌beacon/‌pull/‌39
>> https://‌github.com/‌w3c/‌web-platform-tests/‌pull/‌4024
>> Performance Timeline: issues#66
>>
>> timeline: https://‌github.com/‌w3c/‌performance-timeline/‌issues/‌66
>> Q: is this L2 or L3 feature?
>> we'll revisit next time.
>> Navigation Timing: Set `name` to document address
>>
>> Set `name` to document address: https://‌github.com/‌
>> w3c/‌navigation-timing/‌pull/‌61
>> shipping in M57 in Chrome, stable ~mid march
>> we'll pause landing it until we have confidence in it
>>
> Could you clarify "pause landing it"? Do we need to rollback the change in
> M57 (probably bit late)?
>
>
>> Administrative stuff
>>
>> next: charter update
>> Todd: we need/want charter update from MSFT end
>> … I'll review and merge, first pass looks good
>> we'll followup with plh@ on next steps
>> https://‌github.com/‌w3c/‌page-visibility/‌issues/‌25#issuec
>> omment-262263862
>> xiaoqian: we probably need a test for prerender.
>> AI: let's start a new issue on the repo
>> we'll wait for PR until we resolve ^
>> https://‌github.com/‌w3c/‌hr-time/‌issues/‌32
>> Todd: there are tests in the WPT tree that require user input
>> https://‌github.com/‌w3c/‌resource-timing/‌issues/‌92#issuec
>> omment-283204910
>> L2 CR for UT: https://‌github.com/‌w3c/‌user-timing/‌issues/‌19
>> Todd: I'll try to get the updated tests.
>> We'll try to triage UT2 issues before next call
>> next call: March 22nd
>>
>> ==============
>>
>> On 1 Mar 2017, at 7:59 AM, Ilya Grigorik <igrigorik@google.com> wrote:
>>
>> Hangout: https://hangouts.google.com/hangouts/_/chromium.org/webperf-wg
>>
>> --- Agenda:
>>
>>    - *Using User Timing at scale *-- Dan Abramov
>>
>>    - *Beacon*
>>       - Enforce payload limits via Fetch API:
>>       https://github.com/w3c/beacon/pull/39
>>       <https://github.com/w3c/beacon/pull/39>
>>       - Updates to webplatform tests
>>
>>       - *Performance Timeline*
>>       - Feature detection note: https://github.com/w3c/perform
>>       ance-timeline/pull/70
>>       - Should we tackle takeRecords as part of L2? See
>>       https://github.com/w3c/performance-timeline/issues/66
>>       <https://github.com/w3c/performance-timeline/issues/66>
>>
>>       - *Navigation Timing*
>>       - Set `name` to document address: https://github.com/w3
>>       c/navigation-timing/pull/61
>>
>>
>>    - *Administrative stuff*
>>       - Charter update: https://github.com/w3c/charter-webperf/pull/34
>>       - Adopt Long Tasks, Server Timing?
>>       - Move Page Visibility L2 to PR?
>>          - See https://github.com/w3c/page-vi
>>          sibility/issues/25#issuecomment-262263862
>>          <https://github.com/w3c/page-visibility/issues/25#issuecomment-262263862>
>>       - Move HR-Time L2 to PR?
>>          - One missing test: https://github.com/w3c/hr-time/issues
>>       - Missing TAO test is blocking RT L1..
>>          - https://github.com/w3c/resource-timing/issues/92
>>
>>
>>
>
Received on Tuesday, 7 March 2017 12:05:53 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 7 March 2017 12:05:54 UTC