5 ms·
Maglev: Chrome’s New JIT Compiler
- gravypod 3y ago(Opinions are my own) Funny name clash: https://research.google/pubs/pub44824/ https://research.google/pubs/pub44824/
- deleted 3y ago[deleted]
- jchw 3y agoAs a xoogler, I was thinking the same thing. I assume they knew from the get-go, because well, I can't see how they wouldn't. But I guess it doesn't matter all that much, anyway.
- 1letterunixname 3y agoHave to have a successful internal brand to avoid the next round of layoffs. Now with extra stretch milestones!
- ksec 3y agoAnd Maglev is also an Ruby JIT [1] compiler [1] https://maglev.github.io https://maglev.github.io
- saagarjha 3y agoThis doesn’t really say much about how it works :(
- deleted 3y ago[deleted]
- ksec 3y ago>The most relevant web benchmarks today are Speedometer, MotionMark, and Jetstream. Being a Mid-Tier JIT, am I correct to assume ( I may be wrong ) it brings very little benefits to my day to day browsing if most of my usage are Web page only? My only JS heavy site is Feedly, second being Twitter. I am thinking if there are any benchmarks for testing JPEG, Photos, HTML and CSS Rendering responsiveness and speed.
- pawelmurias 3y agoWithout the sites being JS heavy shouldn't everything be fast enough already?
- killingtime74 3y agoThis is a JIT for JavaScript...Why would you benchmark non JavaScript things.
- verwaest 3y agoActually this concern is exactly why we built Maglev: A very fast JIT that can generate decent enough code very early so it can help even if you're not running tight benchmarks. In fact, the JIT by itself isn't particularly good at the traditional benchmarks yet. It's just very fast, and the code is most often good enough for real browsing usecases.
- sroussey 3y agosrc: https://chromium.googlesource.com/v8/v8/+/refs/heads/main/src/maglev/ https://chromium.googlesource.com/v8/v8/+/refs/heads/main/sr...
- Genbox 3y agoHow devs can work with code that breaks at 80 characters in this day and age is beyond me.
- birdboat00 3y agoimho modern code is in general no very readable a lot of the time.
- grumpyprole 3y agoLots of performance benchmarks but no measurements for power efficiency. Granted this is not easy, but it's more of a requirement than developing more performance benchmarks IMHO. My guess is that most people would rather Chrome improve power efficiency as a priority, which is why many use Safari on the Mac instead of Chrome.
- seanmcdirmid 3y agoI thought chrome was really popular on Macs? It’s on iOS where safaris rules.
- deleted 3y ago[deleted]
- artoale 3y agoYeah, I believe you're right: https://netmarketshare.com/browser-market-share.aspx?options=%7B%22filter%22%3A%7B%22%24and%22%3A%5B%7B%22platform%22%3A%7B%22%24in%22%3A%5B%22Mac%20OS%22%5D%7D%7D%5D%7D%2C%22dateLabel%22%3A%22Trend%22%2C%22attributes%22%3A%22share%22%2C%22group%22%3A%22browser%22%2C%22sort%22%3A%7B%22share%22%3A-1%7D%2C%22id%22%3A%22browsersDesktop%22%2C%22dateInterval%22%3A%22Monthly%22%2C%22dateStart%22%3A%222022-04%22%2C%22dateEnd%22%3A%222023-03%22%2C%22segments%22%3A%22-1000%22%7D https://netmarketshare.com/browser-market-share.aspx?options...
- ygra 3y agoThey do mention reduced power consumption in the opening paragraph. Usually executing the code you want to execute faster also translates to the CPU sleeping earlier again and this increased battery life.