Description

The profiler seems to be most useful when combined with the WebProfilerBundle toolbar, and I suspect this is the main use-case for the profiler. The toolbar is only injected for HTTP requests, but the profiler runs and applies its overheads during CLI operations (console commands) also. I suggest there should be an option to control whether profiling is performed for CLI requests, and that it should be disabled by default in the CLI environment (BC break).

Example

framework:
  profiler:
    cli: false