-
-
Notifications
You must be signed in to change notification settings - Fork 619
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(Investigation) Multi-process support in tracy #822
Comments
Report I got back on the multiplexer work, trying to figure out the reason of the failure. What is still confusing is that the experimental profiler (as I read it) seems to want to consider all client-issued
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is not a bug report, but rather an attempt at documenting my work on #471.
I am still not experienced in the tracy code base, so I'd like to document a bit closely what I try, and what it gave.
What happened today
Worker
is a very central class that manages all the relevant data about a profiling runtracy
does a lot of internal data "compression"uint16_t
export-csv
gave me good insights on the important internal data structures ofWorker
import-chrome
on the other side shows how to feed data into aWorker
I tried testing #766 but I had no success so far, I get the error reported in #766 (comment)
To get my hands dirty, I explored an alternative approach that only supports offline files, let's call it
tracy-merge
.tracy-capture
processes)tracy-merge
on the set of generated*.tracy
, to generate one file that contains all the eventsWorker
. Basically I fill a big vector with events of all the profiling files in turn, taking care of re-mapping thread IDs to avoid overlapsCurrent result, generated from merging the same profiling run from
test/test_cpp
copied twice.The text was updated successfully, but these errors were encountered: