stdx VS flamegraph

There's none that I know of, aside from stdx which was last updated 4 years ago.

⭐ stdx - The missing batteries of Rust - Brian Anderson

brson had a repository called https://github.com/brson/stdx and it's a pity it isn't maintained anymore: some of them are in disuse now (for example, instead of lazy_static prefer stdlib's Lazy, or better yet, you don't need them if you just want to initialize a mutex or something; also error-chain) and the list could use some maintenance

You suggested creating a super-library of vetted crates. It has been tried before, but it didn’t get any adoption. stdx - The missing batteries of Rust was never used much. Looking at it now, it recommends crates that have been superseded by others.

As an example of the above, if you're not aware of it already, you might find brson/stdx interesting.

Big libraries like Boost or the Python standard library tend to develop as a workaround for weak package management so, with Cargo, efforts to produce Boost-like compilations (Eg. stdx) withered on the vine for lack of sufficient interest.

It's been suggested and people even tried doing that of their own volition with projects like stdx, but they withered away for lack of interest.

I second u/globulemix' attitude, searching on crates.io and then looking at Downloads and also git activity (might be misleading, as some projects are simply very stable). For a lot of tasks, you might wish to take a look at stdx

Seems abandoned, but there was https://github.com/brson/stdx

You can install cargo-flamegraph with cargo install flamegraph. There are some underlying requirements to be able to use cargo-flamegraph; you will want to take a look at the repo here to make sure you have the right dependencies.

I tried to diagnose the issue with flamegraph, but unfortunately the flamegraph didn't show anything beyond the next call for some reason

having some tools to identify slowness origins (flamegraph is one... but not sure it's the way to go)

I'm currently implementing a solution for the first part of the day 16. It work but it is really slow... I'd like to : - understand why - having some tools to identify slowness origins (flamegraph is one... but not sure it's the way to go) - eventually have some clue/solution/idea - have general feedback on what in my "coding style" is not appropriate for rust (I come from java/kotlin/ts even if I've already coded a bit in c/c++) : for example I love iterator & sequence but i feel they are not really suited to overuse in rust (mostly because of async & result).

Use a profiler. Flamegraph is a good way to visualise profiler output. This lets you identify which functions are taking up a large amount of time - and hence helps you identify where to focus your optimisation efforts.

You tried trying to see what takes the most time under load via flames? https://github.com/flamegraph-rs/flamegraph

Well, in cases like that the answer is straight forward, use a profiler like https://github.com/flamegraph-rs/flamegraph

I don't see any obvious problems with your algorithm. I've had luck using cargo-flamegraph to identify the slow parts of my code. That's going to show you which parts to focus on improving the performance of!

From the readme of cargo flamegraph: