MozillaZine

Javascript Performance Thread

Discussion about official Mozilla Firefox builds
mayankleoboy1
 
Posts: 364
Joined: February 25th, 2013, 9:52 pm

Post Posted March 4th, 2017, 7:21 pm

greg86 wrote:Why isn't there any progress on any Benchmark on the front page of AWFY in the last month?
I know Sunspider isn't that representative any more but why its staying at the front page?
Are there any better "modern" Benchmarks that show more the improvements in the JS Engine?


AFAIU, the JS team is not specifically trying to improve the Octane/Kraken/Sunspider benchmarks. They are mostly trying to improve more "real-world" code.
They have been working on the CacheIR work, but keep side-tracking to improve other stuff, like Google Docs, six-speed and others.

jandem
 
Posts: 91
Joined: September 18th, 2008, 2:57 pm

Post Posted March 5th, 2017, 3:58 am

A lot of the CacheIR work so far has been converting existing code and fixing performance issues that show up on real-world code. We've fixed a lot of stupid performance issues there, but the shell benchmarks improve less from that because over the years we've spent a lot of time investigating these and we fixed the worst problems a long time ago. Now that the most complicated IC code has been converted to CacheIR, we can spend more time adding new optimizations. Bug 1328140 for instance should definitely help some of the shell benchmarks and pave the way for further improvements there. Hopefully later this month I will have some time to look into some of these benchmarks.

mayankleoboy1
 
Posts: 364
Joined: February 25th, 2013, 9:52 pm

Post Posted March 6th, 2017, 8:18 am

@Jandem:
Any plans to bring back https://bugzilla.mozilla.org/show_bug.cgi?id=785905 ?

jandem
 
Posts: 91
Joined: September 18th, 2008, 2:57 pm

Post Posted March 11th, 2017, 6:39 am

mayankleoboy1 wrote:@Jandem:
Any plans to bring back https://bugzilla.mozilla.org/show_bug.cgi?id=785905 ?

If I remember correctly, the performance win from that was never very big (smaller than I expected) and moving all of IonBuilder off-thread is hard. It would probably be simpler to move some parts of it to the compilation thread. We should look into this again at some point, but for now there are still a lot of potential perf improvements elsewhere.

Timvde
 
Posts: 262
Joined: February 7th, 2013, 3:19 pm

Post Posted March 11th, 2017, 9:04 am

Would you mind making a list? I am very curious what the JS has planned for the future!

mayankleoboy1
 
Posts: 364
Joined: February 25th, 2013, 9:52 pm

Post Posted March 11th, 2017, 10:06 am

Timvde wrote:Would you mind making a list? I am very curious what the JS has planned for the future!


For starters, I would say all the deps of https://bugzilla.mozilla.org/show_bug.cgi?id=1259927 , specially https://bugzilla.mozilla.org/show_bug.cgi?id=1324561 . From the comment, fixing that bug would lead to more cases open to optimization.

Timvde
 
Posts: 262
Joined: February 7th, 2013, 3:19 pm

Post Posted March 19th, 2017, 8:27 am

Google enabled TurboFan (new optimizing engine) and Ignition (interpreter) by default: https://chromium.googlesource.com/v8/v8 ... 40d600d6fc

It cost them on all AWFY benchmarks, but most notably of course on Octane. I didn't expect them to already flip the switch.

It also looks like there's a new benchmark suite, Six Speed: https://www.arewefastyet.com/#machine=2 ... =six-speed / https://kpdecker.github.io/six-speed/

Return to Firefox Builds


Who is online

Users browsing this forum: Google [Bot] and 2 guests