Extract Tracing tools from ayon-cpp-api and implement a perTracing system
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- devtools, performance
Research direction
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.
Written by the indexing model from the issue text.
Description
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
- Dominant language
- C++
- Stars
- 0
- Forks
- 2
- Avg merge
- 4d 7m
- Merged PRs (30d)
- 3
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ynput/ayon-cpp-dev-tools
-
CMake Presets Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in ynput/ayon-cpp-dev-tools
Similar issues
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 88/100
QuantStack/git2cpp#187 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
mlcommons/mobile_app_open#1182 ·
-
Needs-Triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/winget-cli#6547 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·