llvm-propeller
coz
Our great sponsors
llvm-propeller | coz | |
---|---|---|
6 | 18 | |
332 | 3,923 | |
0.9% | 4.6% | |
0.0 | 5.7 | |
7 months ago | 9 days ago | |
Shell | C | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
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.)
[1] https://github.com/google/llvm-propeller
-
LLVM Now Using PGO for Its x86_64 Windows Release Binaries: ~22% Faster Builds
Propeller does this: https://github.com/google/llvm-propeller/blob/main/Docs/Opti...
-
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
-
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
coz
- Coz: Causal Profiling
- Coz: Finding code that counts with causal profiling
-
Why is SwitchToThread using so many resources?
But let's take the guesswork out of profilers. Use Coz. It's a causal profiler that performs experiments to determine what code would see the greatest performance improvement of the whole program if made faster. There's a video in the link; I think the best demonstration they had was a program that saw the greatest improvement by optimizing a function that ranked #30 by a sampling profiler.
-
Performance analysing tools
Coz. It's in a Debian package so you don't have to build it. Watch the video embedded in the page I linked; I;m all about profiling, but the devil is if you're not a statistician, you don't know how to read profiler results.
-
How much does Rust's bounds checking actually cost?
I think https://github.com/plasma-umass/coz solves most problems related to noise in benchmarks.
-
Why would introducing a panic cause a 20% performance increase
Perhaps you're thinking of the coz profiler (https://github.com/plasma-umass/coz)?
- Coz: Finding Code That Counts with Causal Profiling
-
Ask HN: Has anyone used Coz for casual profiling?
I was thinking of doing some kernel profiling, and stumbled upon this interesting repo: https://github.com/plasma-umass/coz
I'm pretty intrigued by the concept, and was wondering if anyone here tried out Coz.
-
Best accurate way to measure/compare elapsed time in C++
https://github.com/plasma-umass/coz https://youtu.be/7g1Acy5eGbE
-
Performance variation when moving functions between files
Could it be an issue of binary layout? Have a look at the coz profiler which has a rust port.
What are some alternatives?
BOLT - Binary Optimization and Layout Tool - A linux command-line utility used for optimizing performance of binaries
Sampling Profiler for Python - Simple Python sampling profiler
cargo-xtask
php-spx - A simple & straight-to-the-point PHP profiling extension with its built-in web UI
cargo-pgo - Cargo subcommand for optimizing Rust binaries/libraries with PGO and BOLT.
stabilizer - Stabilizer: Rigorous Performance Evaluation (llvm-12 fork)
nng - nanomsg-next-generation -- light-weight brokerless messaging
zmqpp - 0mq 'highlevel' C++ bindings
MTuner - MTuner is a C/C++ memory profiler and memory leak finder for Windows, PlayStation 4 and 3, Android and other platforms
uvw - Header-only, event based, tiny and easy to use libuv wrapper in modern C++ - now available as also shared/static library!
stabilizer - Stabilizer: Rigorous Performance Evaluation
Kalman - Kalman Filter