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

Simd.js support #210

Open
bnolan opened this issue Jul 5, 2015 · 4 comments
Open

Simd.js support #210

bnolan opened this issue Jul 5, 2015 · 4 comments

Comments

@bnolan
Copy link

bnolan commented Jul 5, 2015

With simd.js support getting closer to released browsers, it might be worth investigating what parts of cannon can benefit from SIMD instructions.

https://blog.mozilla.org/javascript/2015/03/10/state-of-simd-js-performance-in-firefox/

@joates
Copy link

joates commented Jul 20, 2015

+1

@schteppe how do you feel about branching the codebase so that you can accept PRs & run some benchmarks while this is a draft specification ?
(without adversely affecting the current stable build)

@schteppe
Copy link
Owner

Sounds cool! I made a new branch for SIMD.js stuff: https://github.com/schteppe/cannon.js/tree/simd

Some thoughts from me:

  • Can we keep compatibility with non-SIMD browsers?
  • Will we need to change the API much?
  • Benchmarks can be done with benchmark.js. Or is there something better?

@bnolan
Copy link
Author

bnolan commented Sep 15, 2015

We can use a polyfill to emulate SIMD in non-compatible browsers (hopefully if it's implemented well using float32arrays it'll still be just as fast), and it might be helpful porting some of cannon to use array buffers anyway!

@bnolan
Copy link
Author

bnolan commented Sep 15, 2015

I think we should endeavour to not change the API at all, the cannon api is great fun to use. :)

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

3 participants