cargo-pgo
llvm-propeller
Our great sponsors
cargo-pgo | llvm-propeller | |
---|---|---|
3 | 6 | |
431 | 331 | |
- | 0.6% | |
6.8 | 0.0 | |
about 4 hours ago | 6 months ago | |
Rust | Shell | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cargo-pgo
-
Speeding up the Rust compiler without changing its code
Maybe better yet, I have created a cargo subcommand for this! :) https://github.com/Kobzol/cargo-pgo
-
Has anyone had any experience using PGO + BOLT for performance?
There is this cargo command cargo-pgo but i haven't used yet.
-
`cargo-pgo`: cargo subcommand for optimizing binaries with PGO and BOLT
You can find the tool here. I would be glad for any feedback.
llvm-propeller
-
Speed of Rust vs. C
> In theory, Rust allows even better optimizations than C thanks to stricter immutability and aliasing rules, but in practice this doesn't happen yet. Optimizations beyond what C does are a work-in-progress in LLVM, so Rust still hasn't reached its full potential.
Really glad to see this mentioned, I search for it in every post like this.
LLVM should follow now that the mutable noalias bugs appear to be fixed. Remember when it was a meme that every time it gets enabled in rustc, it has to be disabled again in the next .1 release? It's been left enabled for years.
The biggest challenge here is that most people aren't looking for optimizations beyond what they were already getting with C. Like when Google was switching from GCC to Clang, they'd pick apart the asm and report bugs for Clang and LLVM to converge on GCC. That was a big part of why the performance gap closed over the years. But that was closing a gap, not speculatively overtaking them.
Then there's a whole other angle; we now know just how much machine code layout can affect real-world performance, in most cases much more than aliasing rules, but we still haven't made it a seamless part of our build tooling. PGO is now fairly easy, but BOLT is still a pain to integrate for no clear reason, and PROPELLER has been left in an embarrassing state where even its own PDF link is broken [1]. (To be fair, it may not be Google's highest priority at this time.)
-
Speeding up the Rust compiler without changing its code
Looks like they deleted their branches. The latest commit I could find (via pr#11) seems to have the PDF. https://github.com/google/llvm-propeller/tree/424c3b885e60d8ff9446b16df39d84fbf6596aec
Seeing BOLT is becoming increasingly mainstream while nobody has even heard of PROPELLER, it looks like Google abandoned PROPELLER before finishing the upstreaming. In fact, the official link to the paper is now a 404, meaning not only is every article's link to the paper broken, but the GitHub repo's own link to its own paper is broken. Not even Wayback Machine seems to have it because of how GitHub embeds a PDF reader.
-
Performance variation when moving functions between files
Google also wrote PROPELLER which claims to be even better than BOLT, but I don't know why they didn't drive it all the way to upstream. BOLT got merged after PROPELLER claimed to obsolete it. I can only assume there was a lot more to the story than anyone is saying in public.
- AV1 related job offer :O
What are some alternatives?
BOLT - Binary Optimization and Layout Tool - A linux command-line utility used for optimizing performance of binaries
coz - Coz: Causal Profiling
cargo-xtask
cross - “Zero setup” cross compilation and “cross testing” of Rust crates
rsmgclient - Memgraph database adapter for Rust programming language.
cross - “Zero setup” cross compilation and “cross testing” of Rust crates [Moved to: https://github.com/cross-rs/cross]