The actual issue is parallelising it appropriately -- realistically the best you can do (with this approach) is hoist computation into a worker (which i'm working on) and you get hit by data transfer costs at that point as workers do not allow any form of data sharing between threads.
I'm not sure if there is any way to feasibly improve threading of computation in a non-shared-state threading model.
Comments
Definitely something that would benefit from the new Javascript "web workers" (worker threads). http://blog.mozbox.org/post/2009/04/10/Web-Workers-in-action
The actual issue is parallelising it appropriately -- realistically the best you can do (with this approach) is hoist computation into a worker (which i'm working on) and you get hit by data transfer costs at that point as workers do not allow any form of data sharing between threads.
I'm not sure if there is any way to feasibly improve threading of computation in a non-shared-state threading model.
web workers don't have DOM access.
I doubt updating the UI is real processor-intensive. The worker threads would do the math without blocking the UI.