3 ms·

Also core count is increasing, but raw speed per core really isn't. Multicore really doesn't help web rendering very much. Nearly all javascript out there is si

Also core count is increasing, but raw speed per core really isn't. Multicore really doesn't help web rendering very much. Nearly all javascript out there is single threaded and most dom rendering is too.

VMG 14y ago
> Nearly all javascript out there is single threaded and most dom rendering is too. http://en.wikipedia.org/wiki/Web_worker http://en.wikipedia.org/wiki/Web_worker
- gliese1337 14y ago
  That's really not a rebuttal. Yes, lots of browsers now support web workers. Yes, it is therefore possible to write multithreaded javascript. And that may become more common over time. But for now, the fact that it's possible does not change the fact that nearly all javascript is still single threaded.
  - Joeri 14y ago
    IE10's chakra engine parallelizes interpreted javascript execution (on page load) with JIT compilation and garbage collection. So you can have up to three cores at work executing javascript even without web workers. Meanwhile, the rendering subsystem offloads to the GPU, and the whole thing can exist multiple times for multiple tabs, potentially involving dozens of cores executing your web apps. http://blogs.msdn.com/b/ie/archive/2012/06/13/advances-in-javascript-performance-in-ie10-and-windows-8.aspx http://blogs.msdn.com/b/ie/archive/2012/06/13/advances-in-ja...
    - indiecore 14y ago
      Of course all of this is useless in the context of mobile web views because Android dropped web workers and IOS just picked them up.
JoelSutherland 14y ago
Raw speed per core is increasing DRAMATICALLY in mobile. Faster than even Moore's law would dictate. As the die process has shrunk, more transistors are fitting within the mobile TDP ceiling so modern processor methods are finally getting used. As recently as the ARM A8, out-of-order execution wasn't even used! You can verify that this is correct by looking at any benchmark.
bzbarsky 14y ago
> Multicore really doesn't help web rendering very much. There are people working on changing that, for what it's worth.
- erichocean 14y ago
  Indeed. Blossom[0], a mobile MVC client framework for business apps, is being updated as we speak to split apps into a UI/animation thread, with the application/model layer/network in a web Worker on a separate thread. Disclaimer: I wrote Blossom. [0] https://github.com/erichocean/blossom https://github.com/erichocean/blossom
  - erichocean 14y ago
    Why are people downvoting this?
  - bzbarsky 14y ago
    There is also work from the other side, to make the browser engines take more advantage of parallelism. That's more what I was referring to. Blossom sounds pretty neat!

VMG 14y ago

> Nearly all javascript out there is single threaded and most dom rendering is too. http://en.wikipedia.org/wiki/Web_worker http://en.wikipedia.org/wiki/Web_worker

gliese1337 14y ago
That's really not a rebuttal. Yes, lots of browsers now support web workers. Yes, it is therefore possible to write multithreaded javascript. And that may become more common over time. But for now, the fact that it's possible does not change the fact that nearly all javascript is still single threaded.
- Joeri 14y ago
  IE10's chakra engine parallelizes interpreted javascript execution (on page load) with JIT compilation and garbage collection. So you can have up to three cores at work executing javascript even without web workers. Meanwhile, the rendering subsystem offloads to the GPU, and the whole thing can exist multiple times for multiple tabs, potentially involving dozens of cores executing your web apps. http://blogs.msdn.com/b/ie/archive/2012/06/13/advances-in-javascript-performance-in-ie10-and-windows-8.aspx http://blogs.msdn.com/b/ie/archive/2012/06/13/advances-in-ja...
  - indiecore 14y ago
    Of course all of this is useless in the context of mobile web views because Android dropped web workers and IOS just picked them up.

JoelSutherland 14y ago

Raw speed per core is increasing DRAMATICALLY in mobile. Faster than even Moore's law would dictate. As the die process has shrunk, more transistors are fitting within the mobile TDP ceiling so modern processor methods are finally getting used. As recently as the ARM A8, out-of-order execution wasn't even used! You can verify that this is correct by looking at any benchmark.

bzbarsky 14y ago

> Multicore really doesn't help web rendering very much. There are people working on changing that, for what it's worth.

erichocean 14y ago
Indeed. Blossom[0], a mobile MVC client framework for business apps, is being updated as we speak to split apps into a UI/animation thread, with the application/model layer/network in a web Worker on a separate thread. Disclaimer: I wrote Blossom. [0] https://github.com/erichocean/blossom https://github.com/erichocean/blossom
- erichocean 14y ago
  Why are people downvoting this?
- bzbarsky 14y ago
  There is also work from the other side, to make the browser engines take more advantage of parallelism. That's more what I was referring to. Blossom sounds pretty neat!