Hosted by
Google
Call For Participation
| Date | Event |
|---|---|
| 28 September | Call For Participation issued. |
| 29 October | Deadline for statement of interest. |
| 2 November | Deadline for registration. |
| 8 November | Workshop |
| W3C Organization Sponsors |    |
| Workshop Sponsor |  |
There is a an industry-wide momentum towards adopting HTML5 and its series of companion specifications to deploy applications based on the Open Web Platform. Some of those applications are facing however challenges with regards to performance. While Web browsers are improving their implementations on an ongoing basis, not all of those performance issues are due to the speed of the implementations.
Goal
The goal of the Web Performance Working Group is to provide methods to enhance aspects of application performance of user agent features and APIs. The Group is currently looking for use cases and ideas for its third chartered period.
During the group's first charter it advanced Navigation Timing to Proposed Recommendation. The specification is stable and deployed.
During the second charter, the group published Resource Timing, Page Visibility, and the requestAnimationFrame function and a few others.
During the third chartered period, the group will continue efforts around testing and implementation of those specifications. There are several items currently being considered by the Working Group:
- HTTP Archive (HAR) format, which allows a client to export detailed performance data about web pages it loads. See draft specification.
- Memory Measurements, for information about memory consumption, how much memory each asset uses, how much memory remains available, etc.
- Network Measurements, for information about network resources consumed by an app, bandwidth usage, keep-alive information, etc. Can we improve mobile data connection?
- Network Streaming Measurements, for information about media stream speeds, etc. Measurements related to the HTML5 Media Source Extension.
- Framerate Measurements, information about actual application framerates (which may be less than the maximum device refresh rate).
- Garbage Collector API, which lets app developers control the behavior of the JavaScript garbage collector (e.g., disable during redisplay, or trigger at a moment known to be unobtrusive).
- Diagnostics API: A unified API for diagnosing the performance of Web applications exposing the same information (JS profiling, memory profiling, rendering, etc.) as Chrome Developer Tools, Firebug and similar tooling.
In addition, we look forward to your input on high-priority performance issues that we need to address to ensure the broad deployment of the Open Web Platform.
Workshop participants will:
- Share current experience with performance issues on the Web;
- Examine current technology, including W3C standards, to understand how well the Web does or does not with regards to performance;
- Identify roles for W3C and next steps for work at W3C to make the Open Web Platform performant;
- Help the Web Performance Working Group to prioritize their next work items.
Survey
Independently of the workshop participation, we encourage Web application authors at large to provide feedback through our survey.
Audience
W3C encourages implementers and Web application authors interested in improving the performance of the Open Web Platform to participate in the Workshop.
Requirements for Participation
- There is no participation fee, but registration is required. Registration instructions will be sent to accepted participants.
- W3C membership is not required in order to participate in the Workshop.
- Each participant must submit (or be co-submitter of) a statement of interest.
- The total number of participants will be limited. To ensure diversity, a limit may be imposed on the maximum number of participants per organization.
- Press representatives must contact w3t-pr@w3.org.
Statement of Interest
Statements of interest will be the basis for the discussion at the Workshop. The statement of interest could list performance issues that you have experienced and would like to solve (it is not required to propose solutions in the statement, just listing the issue would suffice). It could be specific web application use cases you'd like browser implementations to support with good performance. If you have tests to illustrate an issue or use case, please share them as well.
Statements must be submitted no later than 29 October 2012. Late submission of statements may be accepted depending on space availability.
Statements of interest must be submitted via email to team-workshop-submissions@w3.org, an archived mailing list accessible to the W3C Team. Feel free to simply point us to a public document if you prefer. Don't hesitate to contact Philippe Le Hégaret (plh@w3.org) before October 29, if you think your statement got lost.
The Program Committee may ask the authors of particularly salient statements to explicitly present their position at the Workshop. Presenters will be asked to make the slides of any presentations available to the public in HTML, PDF, or plain text.
Workshop Organization
Workshop sessions and documents will be in English.
- Chairs:
- Arvind Jain, Google
- Jason Weber, Microsoft
- Team Contact:
- Philippe Le Hégaret, W3C
Venue
The Workshop will be hosted by Google in their headquarter offices in Mountain View, California, USA.
Deliverables
A report will also be published online.