cheatsheets
cargo-asm
cheatsheets | cargo-asm | |
---|---|---|
1 | 13 | |
2 | 1,104 | |
- | - | |
0.0 | 0.0 | |
over 2 years ago | about 2 years ago | |
TypeScript | Rust | |
MIT License | 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.
cheatsheets
-
How can I profile this type of slowdown?
You can see my flamegraph here, it's not very clear that the clone is taking up a lot of time. Is there some tool that gives me a percentage of total time that is spent on one function? Then I could easily see that the clone is taking a long time
cargo-asm
-
Performance difference between obj.function(...) and function(obj, ...) ?
cargo asm might be useful here (if you can't use godbolt).
-
Is there a simple way to borrow the value of an Option without using a match statement?
They should be inlined in release mode. You'd have to verify by checking the assembly, though, which could be done directly in the Rust playground or with a tool like cargo-asm.
-
Hey Rustaceans! Got a question? Ask here (4/2023)!
You can use cargo asm - not sure if you can integrate it with VSCode, but even from a terminal it's a pretty convenient tool.
-
How does rust optimize this code to increase the performance so drastically?
There's probably a built-in one somewhere, but I suspect it'd be easier just to install https://github.com/gnzlbg/cargo-asm
-
Is there a library to display source with annotations?
I don't know if there's a way to do a side by side comparison but cargo-asm uses the source mapping information from rustc to annotate chunks of assembly with it's respective rust code, though it's an imperfect process.
-
Hey Rustaceans! Got a question? Ask here! (25/2022)!
After that you would need some tools to help figure out how to achieve improvements. That will depend on your system and personal preferences. As the other commenter suggested, perf is a good choice on linux. I personally like to look at the generated assembly, using either cargo asm, godbolt, or just rust playground.
-
New crate announcement cargo-show-asm
Doesn't this already exist? https://github.com/gnzlbg/cargo-asm
- on the fly disassembler for Rust symbols
-
Writing the fastest GBDT libary in Rust
From the flamegraph, we knew which function was taking the majority of the time, which we briefly described above. We started by looking at the assembly code it generated to see if there were any opportunities to make it faster. We did this with cargo-asm.
-
How can I profile this type of slowdown?
You're best bet at the moment is probably using cargo-asm to inspect the function assembly to see when it is performing the correct TCO.
What are some alternatives?
rust - Empowering everyone to build reliable and efficient software.
cargo-show-asm - cargo subcommand showing the assembly, LLVM-IR and MIR generated for Rust code
multitarget-issue
safe_arch - Exposes arch-specific intrinsics as safe function (via cfg).
wide - A crate to help you go wide. By which I mean use SIMD stuff.
stateright - A model checker for implementing distributed systems.
tracing - Application level tracing for Rust.
macroquad - Cross-platform game engine in Rust.
tiny-skia - A tiny Skia subset ported to Rust
ili9341-rs - A WIP, no_std, generic driver for the ILI9341 (and ILI9340C) TFT LCD display
LightGBM - A fast, distributed, high performance gradient boosting (GBT, GBDT, GBRT, GBM or MART) framework based on decision tree algorithms, used for ranking, classification and many other machine learning tasks.
realworld-axum-sqlx - A Rust implementation of the Realworld demo app spec using Axum and SQLx.