Closed corsairius closed 1 year ago
Hi @corsairius
Thank you for reporting this!
With the parameters you've provided it seems like you should be seeing 12 minutes in pyroscope.
When the timeslice is selected, the expected visualization would be expected to indicate total execution time
How long is the time slice you've selected? Note that each yellow line corresponds to 10 seconds in real time. So if you're selecting 2 yellow lines, it's normal to see 17.13 seconds of CPU time during those 20 seconds of real time.
It would be helpful if you've provided:
Another thing I'll mention is that currently there might be some profiling data loss at the very end of the process's lifetime. Pyroscope collects data in 10 seconds batches, and so if you have a process that starts at 12:00:00 and ends at 12:00:15, that last 5 second period of time will be lost because the profiling session is not properly finilized. We're working on a long term solution to this problem. For now you can add a 10 second sleep at the end of your script if you really need those last few seconds.
also FYI (not sure if code is too sensitive to post here) but another option instead of screenshots is getting a shareable link via flamegraph.com
Up to you though if you feel comfortable sharing that vs sharing the screenshot :)
I just ran the script, and then a selection of the timeline that is circled should, imho, show the same numbers.
The flamegraph appears different as well. What is the expected visualization after selecting the timeslices?
closing as i believe this is functioning correctly and more an issue of cpu vs wall time. Let us know if you still run into this issue
Discussed in https://github.com/pyroscope-io/pyroscope/discussions/1298