Unity Profiler CPU Sampling Overhead Limits

The Unity Profiler provides critical telemetry for CPU usage and memory allocation, but the granularity of data collection directly impacts the performance of the target device. While standard profiling offers a high-level overview, Deep Profiling provides a comprehensive call-stack analysis for every function call.

A primary constraint is the significant overhead introduced by Deep Profiling, which can skew performance metrics or cause instability on low-end mobile hardware. This creates a conflict between the need for precise bottleneck identification and the requirement to maintain a representative execution environment.

• What are the specific thresholds where Deep Profiling overhead begins to invalidate real-time performance data?
• Is there a documented method to limit Deep Profiling to specific script namespaces to reduce CPU noise?