DRAFT/DISCUSSION: Profiling modifications

[mattw-nws]

How do we (do we?) want to manage a profiling version of ngen? Dev branch? Macros? Replace with better external tool than callgrind?

Additions

Removals

Changes

Testing

Screenshots

Notes

Todos

Checklist

• PR has an informative and human-readable title
• Changes are limited to a single goal (no scope creep)
• Code can be automatically merged (no conflicts)
• Code follows project standards (link if applicable)
• Passes all existing automated tests
• Any change in functionality is tested
• New functions are documented (with a description, list of inputs, and expected output)
• Placeholder code is flagged / future todos are captured in comments
• Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
• Reviewers requested with the Reviewers tool ➡️

Testing checklist (automated report can be put here)

Target Environment support

• Linux

[donaldwj]

The primary difference between the internal profiling and call grind is the internal tools have a much lower time cost but only provide data about broad categories of execution.

[PhilMiller]

Some of this got done in #696 and other bits will need to be reworked, and won't be that hard anyway.