- From: Philippe Le Hegaret <plh@w3.org>
- Date: Wed, 14 Jan 2015 15:54:57 -0500
- To: public-web-perf <public-web-perf@w3.org>
Present: Ilya, Tobin, Michael, plh (late) Meeting notes (thanks to Michael): - surfacing redirect timing data in NT/RT: http://lists.w3.org/Archives/Public/public-web-perf/2015Jan/0006.html Tobin will check with the authors of the original spec, see if we can figure out why some decisions were made regarding redirects. new proposal draft for NEL: http://lists.w3.org/Archives/Public/public-web-perf/2015Jan/0021.html Ilya will check with Mozilla, Chrome is happy with the draft. frame timing + cost: http://lists.w3.org/Archives/Public/public-web-perf/2015Jan/0019.html "cost" is hard problem to get consensus on. Should probably be a separate discussion. cpuTime is challenging for both IE and Chrome to attribute to a frame. IE investigating what would be feasible for them to surface. Feedback on Ilya's document? Separate API to measure/report CPU time in general (arbitrary JS measurement) yoav: cpuTime is really interesting for image decoding time useful to compare codecs and RUM for bytes versus decode time.. not necessarily part of "frame timing" maybe resource timing? javascript stopwatch? Ilya: cpuTime (+gpuTime) measurement - (AI) lets document some use cases. Frame Timing, Image Decoding, Memory utilization? etc. Philippe
Received on Wednesday, 14 January 2015 20:54:59 UTC