I guess “purge 17% of the code” is not the correct answer?
How to make Firefox builds 17% faster
11–20 of 38 posts
Re: How to make Firefox builds 17% faster
#12Re: How to make Firefox builds 17% faster
#13Can 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.
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.
Would it be possible to do somethign like editions for proc macros, or have crates establish "this is a v2 proc macro" or something? There are a lot of things I'd love to see change in a v2 but it'd all be breaking.
Re: How to make Firefox builds 17% faster
#14Can 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.
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.
Do you have a link for this one? Would love to see it.
Re: How to make Firefox builds 17% faster
#15So ... 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.
Obviously it'll make the developer more efficient to spend more time twiddling his thumbs waiting for his code to compile rather than creating a simple build performance win that allows him to, you know, spend more time improving Firefox. Not to mention all the other developers who stand to benefit from faster builds.
Re: How to make Firefox builds 17% faster
#16Can 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.
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.
what do you mean by idempotent and colpike?
Re: How to make Firefox builds 17% faster
#17Earlier quoted context omitted.
Does ccache fetch compiled code from a central server using checksums?
sccache can, but most of us don't have access to an sccache instance: https://github.com/mozilla/sccache
sccache is pretty easy to set up and you can back it with S3, memcache, redis, etc.
Re: How to make Firefox builds 17% faster
#18I’m not too familiar with Firefox builds. Why are clobber builds common? At first glance it seems weird to add a cache around your build system vs fixing your build system.
Re: How to make Firefox builds 17% faster
#19wow, 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.
managing deps as a separate project introduces a lot of day-to-day annoyances, especially if the files are actually changed decently often.
Re: How to make Firefox builds 17% faster
#20I’m not too familiar with Firefox builds. Why are clobber builds common? At first glance it seems weird to add a cache around your build system vs fixing your build system.
Define “fixing.” If you’re building on ephemeral containers, an external cache is necessary for files that don’t change.