Extract Tracing tools from ayon-cpp-api and implement a perTracing system

Performance Tracer Proposal

Preamble

We need to performance test the Cpp software stack.
Currently we dont have a good unified system to performance Trace.
we want both File export tracing and Software Attached Tracing.

the AyonCppApi has an build option to include an function instrumentor.
the code is very simple but allows us to get a file that can be used to visually inspect what functions get called and how much time they need.

we want to move this code into the CppDevTools and improve its functions

Purpose and Problem

• Move the Instrumentor code from the CppApi int othe CppDevTools
• Visualisation via perfetto
• Implement a Perf Testing System that tests at different Request Amounts
  • Show BigO
  • Allow us to see if tools behave at different scales
  • Show this Data as an Graph with data at the data points. https://github.com/ynput/ayon-automator/issues/4
  • Export as CSV data

Research

• The Insturmentor in the CppApi is based on The Chernos instrumentor

Links

• https://github.com/google/orbit
• Gprof, Gprof2dot and Dot https://www.youtube.com/watch?v=zbTtVW64R_I&t=319s

Start by locating the function instrumentor in ayon-cpp-api and reviewing how its build option and file export work. Then inspect the CppDevTools structure and the stated Perfetto, request-scaling, graph, and CSV goals. Done means the tracing tools are moved and the proposed performance-testing capabilities are implemented.