How to support more Tracy functionality

[expipiplus1]

I'd really like to track frames and Vulkan GPU perf with Tracy. I guess that this isn't supported at the moment, and I'm opening this to ask how much work it would be to get something like this in, if it's short of a large rewrite I'd be happy to take it up.

[ethercrow]

Currently we export trace data to Tracy via chrome tracing format that doesn't have these features.

Tracy's internal wire format is not stable and intentionally not advertised in docs, so your best bet would be to first make a Haskell wrapper for Tracy's C API. I imagine it would be usable without opentelemetry as well.

[expipiplus1]

The problem with that is tracking Haskell threads properly. As far as I know its currently not possible with GHC to be informed about the creation/destruction/starting/stopping of haskell threads (which I think are the events required for using the upcoming Tracy fiber work). Regardless, seems like open telemetry isn't a perfect fit here, thanks for the quick response! I'll keep using this until the fiber stuff lands because its good otherwise :)

…

On Wed, Dec 2, 2020, 12:54 AM Dmitry Ivanov ***@***.***> wrote: Currently we export trace data to Tracy via chrome tracing format that doesn't have these features. Tracy's internal wire format is not stable and intentionally not advertised in docs, so your best bet would be to first make a Haskell wrapper for Tracy's C API <https://github.com/wolfpld/tracy/blob/master/TracyC.h>. I imagine it would be usable without opentelemetry as well. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#41 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGRJXCP3NBTUBAFKJ7K46DSSUNUDANCNFSM4UJGMXGQ> .