Web Profiler configuration transition from Symfony 3 to Flex-based versions

Profiling Bottlenecks in Modern Symfony

Identifying performance bottlenecks requires precise measurement using the Web Profiler bundle and the Stopwatch component. In legacy Symfony 3 environments, profiler settings were typically managed within app/config/config_dev.yml. With the transition to Symfony Flex and versions 4 through 7, these configurations have moved to config/packages/web_profiler.yaml and the framework.profiler keys.

While the debug toolbar provides high-level request timing and Doctrine query counts, the overhead of the development container and debug mode can distort absolute measurements. This creates uncertainty when deciding whether the built-in Profiler panels provide sufficient data or if manual instrumentation via Symfony\Component\Stopwatch is necessary to isolate specific code blocks without the noise of the full debug environment.

• How does the current framework.profiler configuration in Symfony 6+ handle the isolation of specific event timings compared to the legacy enable_profiler approach?
• What is the recommended strategy for verifying that Profiler-reported timings are not being skewed by the debug-mode container rebuilds?