profile-coverage

To find gaps in code instrumentation for performance profiling, generate an instrumentation map that classifies uninstrumented functions based on their relevance to the hot path, marking them as 'YES', 'MAYBE', or 'NO' for new instrumentation points.

The best way to identify uninstrumented functions on a hot path is to review profiler instrumentation coverage within specified source directories, analyzing function bodies and public APIs to classify missing measurement points by execution relevance.

Yes, you can review instrumentation coverage for D3D11 and compositor pipelines. The analysis specifically identifies these detailed pipeline areas for targeted review to ensure critical rendering paths are accurately measured.

You prioritize which functions need profiling instrumentation by analyzing function bodies and public APIs to assess their potential for blocking or delaying execution, then classifying each uninstrumented function as 'YES', 'MAYBE', or 'NO'.

You need to review profiler instrumentation across your source code when performance analysis lacks accuracy, ensuring critical code paths are measured by mapping all functions and adding instrumentation to unprofiled hot path areas.