Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is new Ejecta slower than old Ejecta (with custom JSC) ? #597

Closed
finscn opened this issue Dec 28, 2015 · 2 comments
Closed

Is new Ejecta slower than old Ejecta (with custom JSC) ? #597

finscn opened this issue Dec 28, 2015 · 2 comments

Comments

@finscn
Copy link
Contributor

finscn commented Dec 28, 2015

Is new Ejecta slower than old Ejecta (with custom JSC) ?

I see new Ejecta use EJConvertTypedArray for TypedArray, Is it as fast as old Ejecta ?

@phoboslab
Copy link
Owner

The new EJConvertTypedArray is significantly slower than it was in old versions. In old versions Typed Array data access was instant (constant time), while in the current version all bytes have to be copied. However, with the new version, we don't need the custom JSC anymore.

The current way to access Typed Array data is only a workaround until this webkit bug is fixed - so only 1 or 2 more years :/

@finscn
Copy link
Contributor Author

finscn commented Feb 5, 2016

Thanks . maybe I have to use your JSC lib still. My game use many getImageData putImageData

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants