4 ms·
Unfortunately on two machines that I'm using that i7 cores, 16GB of ram, they both seem to have performance problems with layout recalculation. Also I believe
by zghst 13y ago
Unfortunately on two machines that I'm using that i7 cores, 16GB of ram, they both seem to have performance problems with layout recalculation.
Also I believe that many problems that this is trying to solve is already alleviated in existing technologies that will work in modern browsers, including IE10+, and web documents do not necessarily need constraints.
I think contributing to Mozilla or Webkit, or proposing a specification to the W3C would be more advantageous for your cause.
- bergie 13y agoW3C will be the way to go long-term, but first we want to have as much real-world experience with this thing as possible. And that is what the current JavaScript implementation enables for us and others. Specs should never be made in ivory towers! As for performance, that sounds very dubious given that even my Nexus 7 does this thing at 60fps
- drgath 13y agoRunning into the same jank issue as well. Chrome 33, Macbook Pro i7 w/ 16gb RAM. While I'm not at 30fps (averaging in the 40s), there are definitely some frames being dropped. Runs a bit smoother in Firefox.
- TheZenPsycho 13y agocould this be happening because of bad video drivers? gss uses css transforms to speed up rendering and a bad video driver can cause a browser to automatically switch down to software rendering of 3D transforms.
- prewett 13y agoIf GSS requires 3D acceleration to get good performance, I'd say that it needs some serious optimization somewhere. Adding another slow layer is not really helping anything: by the time you have browser-C++-overhead + DOM overhead + JS interpretation/V8/SpiderMonkey overhead, adding another layer on top of this all is really not wanting to make me develop on this platform.