BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20230923T163247Z
BEGIN:VTIMEZONE
TZID:Europe/Madrid
BEGIN:STANDARD
DTSTART:20221030T010000
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
END:STANDARD
BEGIN:STANDARD
DTSTART:20231029T010000
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20230326T010000
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:9a8981ae-8b11-4aff-b2ed-84b8bdecf781
DTSTAMP:20230923T163247Z
SUMMARY:Web Worker Quality of Service
DTSTART;TZID=Europe/Madrid:20230913T143000
DTEND;TZID=Europe/Madrid:20230913T153000
DESCRIPTION:https://www.w3.org/events/meetings/9a8981ae-8b11-4aff-b2ed-84b8
 bdecf781/\n\n**Web Worker Quality of Service**\n\n\n\n\n\n\n\n\n\n\n\n\n\n
 \n\n[Web Workers](https://html.spec.whatwg.org/multipage/workers.html#work
 ers) enable multithreading in web browsers. By offloading compute-intensiv
 e workload to worker threads\, we can achieve better UI smoothness and res
 ponsiveness. Till now\, we have been using a cookie-cutter approach to off
 load such "background" jobs to Web Workers. Compute workloads have varied 
 characteristics\, some tasks are latency sensitive while some can function
  better in a consistent level of performance for prolonged periods of time
 . To satisfy tasks with different performance expectations\, modern CPUs i
 ncorporate a hybrid architecture with high-performance and high-efficiency
  cores. Operating systems have APIs to control a thread's Quality of Servi
 ce (QoS). Under the hood\, hardware schedulering tools look at various per
 formance monitoring units and give hints to the Operating System which mak
 es the decision to deploy the task to a performance core or an efficiency 
 core.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nWe propose introducing a quality of s
 ervice attribute to the Web Workers so that applications and libraries hav
 e a way to explicitly label a worker’s preference of performance. User A
 gents can take this hint to configure platform thread and possibly affect 
 the scheduling policy.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nSee the [Explainer](
 https://github.com/riju/web-worker-quality-of-service/blob/main/explainer.
 md).\n\nAgenda\n\n**Chairs:**\nRijubrata Bhaumik\, Yoav Weiss\n\n**Descrip
 tion:**\n**Web Worker Quality of Service**\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
 [Web Workers](https://html.spec.whatwg.org/multipage/workers.html#workers)
  enable multithreading in web browsers. By offloading compute-intensive wo
 rkload to worker threads\, we can achieve better UI smoothness and respons
 iveness. Till now\, we have been using a cookie-cutter approach to offload
  such "background" jobs to Web Workers. Compute workloads have varied char
 acteristics\, some tasks are latency sensitive while some can function bet
 ter in a consistent level of performance for prolonged periods of time. To
  satisfy tasks with different performance expectations\, modern CPUs incor
 porate a hybrid architecture with high-performance and high-efficiency cor
 es. Operating systems have APIs to control a thread's Quality of Service (
 QoS). Under the hood\, hardware schedulering tools look at various perform
 ance monitoring units and give hints to the Operating System which makes t
 he decision to deploy the task to a performance core or an efficiency core
 .\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nWe propose introducing a quality of servi
 ce attribute to the Web Workers so that applications and libraries have a 
 way to explicitly label a worker’s preference of performance. User Agent
 s can take this hint to configure platform thread and possibly affect the 
 scheduling policy.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nSee the [Explainer](http
 s://github.com/riju/web-worker-quality-of-service/blob/main/explainer.md).
 \n\n**Goal(s):**\nExtend Web Workers to utilize little/E cores. Get Wider 
 Stakeholder feedback.\n\n\n**Materials:**\n- [slides](https://www.w3.org/2
 023/Talks/TPAC/breakouts/web-worker-qos/)\n- [minutes](http://www.w3.org/2
 023/09/tpac-breakouts/47-minutes.pdf)\n- [live google doc minutes](https:/
 /docs.google.com/document/d/16N8ksiOzWLNGxhuagSNAgMcdQOW-KFy4Nn2aGsjf6EA/e
 dit#heading=h.mqwe74gibuzg)\n- [recording](https://www.w3.org/2023/09/brea
 kouts/recording-47.html)\n- [Session proposal on GitHub](https://github.co
 m/w3c/tpac2023-breakouts/issues/47)\n\n**Track(s):**\n- performance
STATUS:CONFIRMED
CREATED:20230905T053937Z
LAST-MODIFIED:20230923T163247Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Nervion I - Level -1
CATEGORIES:TPAC 2023,Breakout Sessions
END:VEVENT
END:VCALENDAR