[Public WebGL] WebKit 20-50% slower than Chrome/Minefield using large Float32Array Arrays

Stephen Bannasch [email protected]
Thu Feb 24 07:28:10 PST 2011

At 9:55 AM -0800 2/24/11, Vladimir Vukicevic wrote:
>I've actually done that in https://bugzilla.mozilla.org/show_bug.cgi?id=636096 that I filed for this issue.
>Stephen, your testcase does two things that will/can skew the results -- first, don't use setInterval, like forget it exists :)  The minimum interval/timeout time is different between browsers... for fastest iteration you'll want to use the postMessage trick.

Ahh ... I don't know the postMessage trick ... I will find out what that is.

>Second, modifying innerHTML inside your benchmark loop is not ideal as that can be a pretty slow operation... certainly valid thing to do for a normal app, but not great for a benchmark unless you're explicitly testing innerHTML setting speed.

There are two rendering methods, only the second uses innerHTML -- it was faster than my original canvas rendering implementation.

The testing reports are all run without rendering.

>(Third, the testcase helped us find a few bugs, thanks :-)

That's great!

Thanks for your comments.
You are currently subscribed to [email protected]
To unsubscribe, send an email to [email protected] with
the following command in the body of your email:
unsubscribe public_webgl

More information about the public_webgl mailing list