4 ms·
Good to see the Webkit team (mostly Apple) continue putting serious energy into JS performance. Take a bit of guts to throw out the whole LLVM layer in order to
by cpr 11y ago
Good to see the Webkit team (mostly Apple) continue putting serious energy into JS performance. Take a bit of guts to throw out the whole LLVM layer in order to get compilation performance...
It's also encouraging to see them opening up about future directions rather than just popping full-blown features from the head of Zeus every so often. (Not that they owe us anything... ;-)
(Edit: it's also damned impressive for 2 people in 3-4 months.)
- MrBuddyCasino 11y agoGutsy move indeed. Though I wonder, what was the development cost in real life cash for gaining those 5% of performance?
- pizlonator 11y ago3 months. Two people working on it (me and @awfulben).
- titzer 11y agoNice work, Fil. Looks cool.
- pizlonator 11y agoThanks! :-) Looking forward to more write-ups about TurboFan!
- MrBuddyCasino 11y agoOk, thats impressive. I'll show myself out.
- ignoramous 11y agoGreat work! Time to update... https://en.wikipedia.org/wiki/WebKit#JavaScriptCore https://en.wikipedia.org/wiki/WebKit#JavaScriptCore
- bluejekyll 11y agoOut of curiousity, did you look at improving LLVM compile times? I didn't get that out of the article. Awesome write up btw.
- om2 11y agoAs Phil said, the development cost was not that high all things considered. But even if it was - think about the number of user-hours that 5% is leveraged across, and the resulting time savings and battery life savings for those users. It would be worth investing even more than we did for 5%!
- ksec 11y agoConsidering there are now 1Billion Active iOS devices, that 5% saving is huge! I wonder if this will make in time for iOS10.