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

RE: [3/22/17] webperf group call @ 10AM PST

From: Todd Reifsteck <toddreif@microsoft.com>
Date: Wed, 22 Mar 2017 06:02:01 +0000
To: Shubhie Panicker <panicker@google.com>, Ilya Grigorik <igrigorik@google.com>, Nolan Lawson <nolawson@microsoft.com>
CC: public-web-perf <public-web-perf@w3.org>
Message-ID: <CY4PR03MB2838CFA7DF92EF257CBD0A91C23C0@CY4PR03MB2838.namprd03.prod.outlook.com>
I have a last-minute doctor conflict, but don’t want to hold the call up. Nolan will attend. My comments inline.


From: Shubhie Panicker [mailto:panicker@google.com]
Sent: Tuesday, March 21, 2017 5:12 PM
To: Ilya Grigorik <igrigorik@google.com>
Cc: public-web-perf <public-web-perf@w3.org>
Subject: Re: [3/22/17] webperf group call @ 10AM PST

I'd like to add another item: surfacing memory related signals to developers.
We've been evaluating couple proposals:
1. surface device memory<https://docs.google.com/document/d/1O0fKj5q4U8EF2LZdScXB6c02laQmixPekG-fuCQUHys/edit> as proxy for (or component of) device class
2. surface memory pressure<https://github.com/WICG/memory-pressure/blob/master/explainer.md> signal (positive signal at TPAC but mixed signals from developers recently)
We'd love to get some early feedback on this.

On Tue, Mar 21, 2017 at 3:18 PM, Ilya Grigorik <igrigorik@google.com<mailto:igrigorik@google.com>> wrote:
Hangout: https://hangouts.google.com/hangouts/_/chromium.org/webperf-wg

# Agenda

  *   Beacon API

     *   Progress on https://github.com/w3c/web-platform-tests/pull/4024

[toddreif] Blocked on other work. Coming in next 1-2 weeks. (Sorry… ☹)

     *   Transition to CR?
[toddreif] Yes, I believe we have sufficient evidence.

  *   Page Visibility L2

     *   Test for prerender: https://github.com/w3c/web-platform-tests/pull/5185

        *   Transition to PR? Blocked on above
[toddreif] Yes, I believe this should work.

  *   HR Time L2

     *   Check-in on prompt to unload test: https://github.com/w3c/hr-time/issues/32

[toddreif] I suggest it be started with a manual test. Any automation will require that as a first step anyway.

  *   Performance Timeline L2

     *   Editorial + cleanup updates PR: https://github.com/w3c/performance-timeline/pull/75

     *   Transition to PR?
[todreif] Both LGTM

  *   Resource Timing

     *   Review TAO tests: https://github.com/w3c/resource-timing/issues/92

        *   Unblocks L1 PR transition
[toddreif] Haven’t had time to review, but don’t block on me. We should validate that IE11/Edge both pass the new tests as we know they implement both old and new version of TAO spec.

  *   Triage open Preload & User Timing issues

     *   https://github.com/w3c/preload/issues

     *   https://github.com/w3c/user-timing/issues

# Administrative

  *   Transition Long Tasks to WG
  *   Transition Server Timing to WG

     *   Blink I2I: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/y3qwr490Fc4

[toddreif] We should transition all specs previously agreed upon.

  *   Next steps on updated charter
[toddreif] Please proceed on this assuming all specs have been added again.

  *   Install PR preview and diff tool on all perf repos?

     *   https://github.com/tobie/pr-preview#install

[toddreif] No opinion. Don’t block on me.

Received on Wednesday, 22 March 2017 06:02:36 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 22 March 2017 06:02:37 UTC