I'm sure there's no reason a competent JIT couldn't make a 128x128 update of just adding numbers together. But that's never what's actually happening, you're always dealing with something more complex than that, and it just rolls over and dies.
-
-
So from Chrome's perf recorder, the "recalc" time is 50ms after the script runs. If I take the script and do the optimized version, it takes ~50ms as well, so it's 50ms/50ms. If I turn up the number of things it sets, and make it set them poorly, it's 423ms/50ms.
-
And if I try to regress it all the way back to the original code that I started with, although I'm not 100% sure exactly what that looked like, it takes 2.67s/50ms. So at least as far as I can tell, the recalc time is always constant.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.