# Xdebug Profiling

Although DDEV has more sophisticated profiling capabilities with [xhprof](<https://ddev.github.io/ddev/en/stable/users/debugging-profiling/xhprof-profiling/index.md>) and [Blackfire](<https://ddev.github.io/ddev/en/stable/users/debugging-profiling/blackfire-profiling/index.md>), it also has built-in support for [Xdebug profiling](<https://xdebug.org/>).

## Basic usage

- Create the directory `.ddev/xdebug`, which is where the output files will be dumped.
- Switch Xdebug to profiling mode by adding this in `.ddev/php/xdebug.ini`:

  ```
  xdebug.mode=profile
  xdebug.start_with_request=yes
  xdebug.output_dir=/var/www/html/.ddev/xdebug
  xdebug.profiler_output_name=trace.%c%p%r%u.out
  ```
- Enable Xdebug with [`ddev xdebug on`](<https://ddev.github.io/ddev/en/stable/users/usage/commands/#xdebug>).
- Make an HTTP request to the DDEV project and the profile will be located in `.ddev/xdebug` directory.
- Analyze it with any call graph viewer, for example [kcachegrind](<https://kcachegrind.github.io/html/Home.html>).
- When you’re done, execute `ddev xdebug off` to avoid generating unneeded profile files.
- You can also toggle Xdebug on and off using `ddev xdebug toggle`.

## Information Links

- [Xdebug profiling docs](<https://xdebug.org/docs/profiler>)
- [kcachegrind](<https://kcachegrind.github.io/html/Home.html>)