Updates:
Status: WorkingAsIntended
Comment #1 on issue 2997 by [email protected]: Chrome 30x slower than
FF executing a emscripted lib
http://code.google.com/p/v8/issues/detail?id=2997
The way the time is measured is wrong/biased: FF does AOT compilation, and
this time is excluded in your measurement, while v8 compiles code as it
sees it. If you change the example to tessellate at every update and update
continuously, you see that the times are actually quite similar: Roughly
5ms compared to roughly 4ms for FF on my machine. The difference is still
there (and expected, we know a few rough edges), but you now exclude the
compilation time and measure throughput.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
