Live data from Hacker News

The Baseline Interpreter: A Faster JavaScript Interpreter in Firefox 70

hacks.mozilla.org

241–250 of 281 posts

Re: The Baseline Interpreter: A Faster JavaScript Interpreter in Firefox 70

#241

Earlier quoted context omitted.

Did you look at the raptor dashboards? Let me help you: https://treeherder.mozilla.org/perf.html#/graphs?timerange=2...

Thank you! But without being able to compare it with chromium the results are meaningless to my brain.

You're free to port it to Chromium and run it yourself.

Re: The Baseline Interpreter: A Faster JavaScript Interpreter in Firefox 70

#242
post #188

What's a good way to diagnose optimzation/deoptimization performance issues? The Z80 emulator I use for http://8bitworkshop.com/ has some long pauses while it's spinning up. It uses a huge generated switch statement, which I'd assume is hard to optimize if type info isn't complete. (I'm replacing it with a simpler emulator which works much better though)

I have written a single javascript program in my life, and it was an emulator for an 8080-based machine. I used https://bluishcoder.co.nz/js8080/ for that part of the emulator, though I had to make some changes to it.

I found the emulator ran 4x faster on firefox than on chrome. The culprit was the main dispatch loop, a 256-entry switch statement. Chrome used a slow fall-back path because there were too many cases. The fix was to have "if (opcode I also tried generating 256 functions and then dispatch to the right sub based on an array of function pointers, but it wasn't any faster than the switch statement.

But that was five year ago, and I'm sure the landscape is different now.

Re: The Baseline Interpreter: A Faster JavaScript Interpreter in Firefox 70

#243

The Mozilla tech blogs are always a good read. Informative and easy to digest. I can only think of one other company blogging with similar consistency/quality: Cloudflare. Firefox performance has seen tremendous gains since their Project Quantum efforts. It mostly feels on par with Chrome for me pretty much everywhere. There is one glaring omission though: a single company where I have problems with FF on multiple ap…

I suggest checking out the Dolphin Emulator tech blogs as well, they're also consistently great in quality. https://dolphin-emu.org/blog/

Re: The Baseline Interpreter: A Faster JavaScript Interpreter in Firefox 70

#244
post #100
post #73

Earlier quoted context omitted.

I have the opposite experience with YouTube. With an AMD GPU on Linux, Chrome churns, drops frames, and stutters horribly on even 1080p videos at 30fps. Firefox, meanwhile, handles 1440p60 video with no problem. Even two such videos simultaneously, on separate monitors. Chrome became inexplicably better for parts of early 2019 (I did not note which versions), but starting 2 or 3 months ago Chrome returned to being un…

Hey, I'm on the chromium videostack team, would you mind filing a bug report for what you see happening with youtube? https://bugs.chromium.org/p/chromium/issues/entry

Asking to do the work of raising a bug to make a product better which is competing with other non profit product is in itself a bit arrogant in my opinion. On top of that the attitude to be lazy to search for the issue which was already marked as won't fix https://bugs.chromium.org/p/chromium/issues/detail?id=137247 is not the right thing to do. I would have appreciated if you have created the issue with the details provided and shared the link her for the op to fill in more details.

Re: The Baseline Interpreter: A Faster JavaScript Interpreter in Firefox 70

#245
post #226

Earlier quoted context omitted.

The big difference is that those executives would be getting money out of those 20% customer base. I seriously doubt that those 20% Firefox users even consider doing a $1 donation.

Firefox makes money from the install base via the search engine default setting. Fairly sure more so than donations

Might be, is there any official numbers?

After all plenty also switch to other search engines.

Re: The Baseline Interpreter: A Faster JavaScript Interpreter in Firefox 70

#246

The Mozilla tech blogs are always a good read. Informative and easy to digest. I can only think of one other company blogging with similar consistency/quality: Cloudflare. Firefox performance has seen tremendous gains since their Project Quantum efforts. It mostly feels on par with Chrome for me pretty much everywhere. There is one glaring omission though: a single company where I have problems with FF on multiple ap…

Yea YouTube performance is nuts! It seems to be exacerbated when playing in full screen or @2x speed as well. Google has been getting better though with supporting FF. They now support Hangouts on FF and Gmail is actually faster for me in FF than it is in Chrome.

On Edge the slowness increases to the point that loading a ZX Spectrum game from tape feels psychologly faster.

A mute point however now with EdgeChrome.

Re: The Baseline Interpreter: A Faster JavaScript Interpreter in Firefox 70

#247
post #124

Earlier quoted context omitted.

To be fair i think this is an exercize in vanity and why not say it, stupidity. Javascript VM´s these days are fairly complex beasts with huge amount of man-hour and expertise. Also technically this would be a inferior solution as compared to what V8 did with its interpreter in Turbofan (and SpiderMonkey are doing now as presented in the article), by generating pure assembly through the turbofan backend (the same tec…

> Javascript VM´s these days are fairly complex beasts with huge amount of man-hour and expertise. You know what else is a MASSIVE time and money sink? C/C++. Combining 2 big and nasty complex stuff you get something even bigger. ---- I don't say to blind rewrite. Is know to be: > an exercize in vanity and why not say it, stupidity. But this must take in account TIME. Right now , is not the time for a rewrite, but is…

The topic of rewrite, i think it depends a lot of the context. Some things might make perfect sense for a rewrite, but i still think that a very optimized with huge amount of man-hour piece of sophisticated and complex C++ codebase like Spidermonkey VM are not one of those things.

Theres no gain in clear performance, unless theres a better algorithm being implemented, no clear gain in productivity, as C++ and Rust are both equaly complex beasts, and with not much gain in security, if you already implemented in "modern c++" and are using smart pointers, including in API´s and moves correctly.

The other gains in security/safety that you might have with Rust, are maybe lost if you think that the C++ codebase have been used and tested in every possible scenario, so a lot of bugs are corrected, and if you think that given this is a Jit VM you will have to use Rust´s unsafe{} in a lot of places, i still think, giving the context, that is not a smart thing to do, and it will be more like a trophy to Rust, but without a more pragmatic and realistic approach to the matter, not focusing properly on results.

Not much gain, you will end with a worse and more buggy JIT in the end, and will have to spend more years, only to get parity to the VM you already had in the first place.

Re: The Baseline Interpreter: A Faster JavaScript Interpreter in Firefox 70

#248

Earlier quoted context omitted.

I wanted to keep using FF despite being a gmail user so much so that I switched to Thunderbird for my emails. I guess Mozilla wins this way.

I did the same and then ditched gmail for payed email service + my domain. Thumderbird is underrated.

Same here. Gmail is only an easy way to aggregate my emails, which I used yahoo for, and eventually might use something else.

Back home, Thunderbird, and the occasional donations.

Re: The Baseline Interpreter: A Faster JavaScript Interpreter in Firefox 70

#249
post #42

Earlier quoted context omitted.

I solve this by using Firefox for all web browsing, and Chrome for gmail/gapps/anything by google. It sucks that we have to do that, but I can't entirely blame them for making their own products work better on their own browser.

> It sucks that we have to do that, but I can't entirely blame them for making their own products work better on their own browser. You mean like MS for a long time did with MSIE? Are we really back in the 90s, back to “This page works best in $one_specific_browser”? This is not the future I was hoping for... On the flip side I can use Linux for almost anything, so i guess it’s not all bad.

Yes, because Google is a cool company, do no evil and such.

Re: The Baseline Interpreter: A Faster JavaScript Interpreter in Firefox 70

#250

Earlier quoted context omitted.

> It sucks that we have to do that, but I can't entirely blame them for making their own products work better on their own browser. You mean like MS for a long time did with MSIE? Are we really back in the 90s, back to “This page works best in $one_specific_browser”? This is not the future I was hoping for... On the flip side I can use Linux for almost anything, so i guess it’s not all bad.

Well .. consider you are back in the 90s ... would you think in general, that this is "the future you was hoping for..."?

I was considering a future of native applications, connected via network protocols, with the browser being used for hypertext documents.
Post reply on HN