How Rust 1.64 became faster on Windows
tomaszs2.medium.com
How Rust 1.64 became faster on Windows
1–10 of 80 posts
Re: How Rust 1.64 became faster on Windows
#2It's great to see every speed up :)
Re: How Rust 1.64 became faster on Windows
#3It's great to see every speed up :)
I think your comments are being suppressed, they're all removed after you post. You might check on that.
Re: How Rust 1.64 became faster on Windows
#4It's great to see every speed up :)
I think your comments are being suppressed, they're all removed after you post. You might check on that.
https://news.ycombinator.com/newsfaq.html
Look at the [dead] section
Re: How Rust 1.64 became faster on Windows
#5Great to see how huge the benefit of profile-guided optimization is. I feel it's one of the more underappreciated techniques. Rust adding support for it on windows, and showcasing what a big improvement it makes on the compiler is pretty big (in addition to just having a faster compiler)
Re: How Rust 1.64 became faster on Windows
#6What is the common consensus on benchmarking test suites in Rust?
From what I understood: Criterion was the gold standard, but there is a built-in benchmark suite but that is only supported in Nightly.
What’s the difference?
Re: How Rust 1.64 became faster on Windows
#7TLDR: Profile guided optimization was not supported on windows. That has been enabled now. So this only helps you if you are compiling on windows and want to go the extra mile of running PGO builds.
Re: How Rust 1.64 became faster on Windows
#8What is the common consensus on benchmarking test suites in Rust? From what I understood: Criterion was the gold standard, but there is a built-in benchmark suite but that is only supported in Nightly. What’s the difference?
Criterion is still the gold standard.
Pros for Criterion over the stdlib: https://github.com/bheisler/criterion.rs#features
Downsides of Criterion: https://bheisler.github.io/criterion.rs/book/user_guide/know...
Re: How Rust 1.64 became faster on Windows
#9Re: How Rust 1.64 became faster on Windows
#10I thought PGO instrumentation works on basic blocks, and the inlining, outlining, and register allocation optimisations are all done on llvm’s IR. So everything can happen in the backend.
What sort of work is OS specific, or language specific?
I’ve used PGO before, but I’m not familiar with the details.