This patchset adds golang trace support to Trace Compass
https://go.dev/blog/execution-traces-2024 <- The trace format and its events were designed around relatively efficient emission, but required tooling to parse and keep around the state of the entirety of a trace. A few hundred MiB trace could require several GiB of RAM to analyze!
This is not the case with the trace compass golang parser. It seems to scale linearly with the trace size. But this is not ready for primetime yet.
In GolangTrace there's a datastructure called "fAwfulBackup" that stores ecery event in ram. It needs to go away before we merge the code.
This patchset adds golang trace support to Trace Compass
https://go.dev/blog/execution-traces-2024 <- The trace format and its events were designed around relatively efficient emission, but required tooling to parse and keep around the state of the entirety of a trace. A few hundred MiB trace could require several GiB of RAM to analyze!
This is not the case with the trace compass golang parser. It seems to scale linearly with the trace size. But this is not ready for primetime yet.
In GolangTrace there's a datastructure called "fAwfulBackup" that stores ecery event in ram. It needs to go away before we merge the code.