HN.zip

How to make Firefox builds 17% faster

116 points by mbitsnbites - 11 comments
mmastrac [3 hidden]5 mins ago
Can you (err... buildcache) cache Rust proc-macros? I've been battling this with sccache and I'm now maintaining a 10-patch deep stack for the next.js build CI.

Windows builds were ridiculously poor on cache hits rates too because of non-determinism that was not able to figure out.

I'd be happy to test it out.

estebank [3 hidden]5 mins ago
There was an experimental PR that treats proc macros as idempotent with the corresponding colpike speed up. I don't know what happened with it, and stabilization required a lot of design work to not break backcompat. But this is something in the team's radar.
allenrb [3 hidden]5 mins ago
I guess “purge 17% of the code” is not the correct answer?
K0IN [3 hidden]5 mins ago
wow, 17% is impressive with such an easy fix. i wonder if we could just build this as a separate project and pull the webidl files as a dependency.
Devorlon [3 hidden]5 mins ago
Why compile code when ccache faster
amelius [3 hidden]5 mins ago
Does ccache fetch compiled code from a central server using checksums?
fishgoesblub [3 hidden]5 mins ago
buildcache, the program the post is about can use a remote server for storing the cache.
01HNNWZ0MV43FF [3 hidden]5 mins ago
sccache can, but most of us don't have access to an sccache instance: https://github.com/mozilla/sccache
shevy-java [3 hidden]5 mins ago
So ... perhaps Mozilla should focus on user share dropping.

I understand that speed is relevant, but focusing on that strategy does not really work when dinosaur-like extinction is around the corner.

tadfisher [3 hidden]5 mins ago
I will just say this: it is unfortunate that you have chosen not to engage with the content of the article.
jeffbee [3 hidden]5 mins ago
Considering that Firefox mainly appeals to its own contributors, making the developer experience better would be important.