y2kappa
Add documentation show how to use chrome://tracing
I only heard about this one month ago so I assume most people are unfamiliar. Documentation with gifs are welcome.
Why not generate a plot using https://github.com/milliams/plotlib or something similar?
It's a good idea, I think we can add an output parameter of how you want to deliver it.
I'd like to keep chrome://tracing as an option for two reasons:
- For myy main use case, I can only print to console, I have no filesystem to save on - it's a docker container / aws lambda function.
- Also, chrome://tracing is pretty sweet, has a lot of built in stuff and interactivity. You can click on individual spans and it shows you the total duration, metadata, etc.
By the way, did you check chrome://tracing with this crate to see how it feels? What do you think a plot can do that chrome://tracing can't?
Haven't tried chrome tracing yet, mainly bc I work with firefox... That's also why I don't know if plots have any advantage here. It's just a widely accepted way of viewing your data.
There is Python's Plotly library which is very rich and easy quite easy to work with, maybe it's a good idea to add a python script to this crate, something like ./visualize.py or something.
(Of course, in addition to chrome tracing, which sounds good)