Transaction profiles

[tilk]

This PR adds transaction profiles. A profile contains a per-cycle information about:

• Which transactions/methods were running. For running methods, which transaction/method called.
• Which transactions wanted to run but couldn't, and which conflicting transaction was running instead.
• Which methods were locked, but not running.

TODO:

• Calculating statistics for the entire profile.
• Options, filtering and sorting in the command line tool.
• Running profile generation in CI to check for regressions.
• Non-inverted call graphs (transactions to called methods).
• User documentation (document the script and the profile option)

In the future:

• Some way of visualizing profiles.

[lekcyjna123]

Overall it looks good. I did some related changes, please check if #552 can be useful.

[lekcyjna123]

According to the point:

Some way of visualizing profiles.

I am currently thinking about two possible way:

• Something similar to waveform, where we have a one timeline for each transaction. It is green if it is running, blue when not ready and red if conflicting, ready and not running
• Graph between transactions and methods. Edges in such graph can visualise how often conflict on these methods/transactions caused a stall of one of them.

[tilk]

I am currently thinking about two possible way:

• Something similar to waveform, where we have a one timeline for each transaction. It is green if it is running, blue when not ready and red if conflicting, ready and not running

• Graph between transactions and methods. Edges in such graph can visualise how often conflict on these methods/transactions caused a stall of one of them.

Both ideas are great, but I think this should be left for a future PR. For now, I'm writing a command-line script which will show transaction and method statistics using inverted call trees (methods to transactions). Normal call trees (transactions to methods) might be useful too.