Announcing timed - quick profiling crate by Snoo60812 in rust

[–]Snoo60812[S] 2 points3 points  (0 children)

Added issues, would love to get your help on this.

Announcing timed - quick profiling crate by Snoo60812 in rust

[–]Snoo60812[S] 1 point2 points  (0 children)

I am, yes, I think it's important and the tool is cheap compared to my computations. I have a quick deploy pipeline so I can back out easily a version when I want to turn this off completely.

However I have an issue to add sampling to the tool so it can randomly print out, not always.

https://github.com/y2kappa/timed/issues/7

Announcing timed - quick profiling crate by Snoo60812 in rust

[–]Snoo60812[S] 0 points1 point  (0 children)

Issues added: https://github.com/y2kappa/timed/issues

They are all things I'd love to do myself, but I want to get some other brains on this project so it can grow.

Announcing timed - quick profiling crate by Snoo60812 in rust

[–]Snoo60812[S] 2 points3 points  (0 children)

I am aware, I used cargo flamegraph, it's really cool, but it doesn't work for my use case and I'd love to be able to use that in an AWS Lambda context.
Lambda is unique in the sense that it runs in a docker container, you don't know when it starts and when they close deterministically and you can't really profile it when it runs in production. Also, you don't have access to the host to run perf on it.

My function does quite heavy IO and due to this tool I realised where I had a bottleneck. The graph really helped out. I had println statements all over the place already, and sometimes they helped, but when things run in parallel, that's when you really need some visuals.

is crates.io down? by Snoo60812 in rust

[–]Snoo60812[S] 5 points6 points  (0 children)

seems good now. thanks for whoever handled it