[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] WebGL perf regression tests moved to GitHub; design still in flux

On 2012/10/02 7:44, Vladimir Vukicevic wrote:
Yup -- it's not that we don't want to measure composite, we're making an end-run around the fact that there exists no API for measuring composite. That API could also be somewhat complicated to define, because each browser could have a very different idea of what it actually means to composite. So, instead, I'm more interested in treating it as "overhead" -- I want to measure how much overhead a browser adds to each frame. This could be compositing overhead, it could be function call/JS bridge overhead, etc. That's where the second attempt comes into play, and it sounds like what gregg's already tried to implement.
I've been thinking about this in respect to WEBGL_dynamic_texture. The best idea I've come up with so far is an event the app can listen for which tells it that the canvas has reached the screen. The event payload would be the  actual timestamp of the start of scanning the composited frame out to the display.

It has been pointed out that firing this every frame would be too much overhead so it should probably be sent every nth frame where n can be specified by the app.



注意:この電子メールには、株式会社エイチアイの機密情報が含まれている場合が有ります。正式なメール受信者では無い場合はメール複製、 再配信または情報の使用を固く禁じております。エラー、手違いでこのメールを受け取られましたら削除を行い配信者にご連絡をお願いいたし ます.

NOTE: This electronic mail message may contain confidential and privileged information from HI Corporation. If you are not the intended recipient, any disclosure, photocopying, distribution or use of the contents of the received information is prohibited. If you have received this e-mail in error, please notify the sender immediately and permanently delete this message and all related copies.