Profile arbitrary code execution.
Code execution happens after WordPress has loaded entirely, which means you can use any utilities defined in WordPress, active plugins, or the current theme.
wp profile eval command by installing the command's package:
wp package install wp-cli/profile-command
Once the package is successfully installed, the
wp profile eval command will appear in the list of available commands.
- The code to execute, as a string.
- Focus on key metrics for all hooks, or callbacks on a specific hook.
- Display one or more fields.
- Render output in a particular format.
- Ascending or Descending order.
- Order by fields.
GLOBAL PARAMETERS GLOBAL PARAMETERS
These global parameters have the same behavior across all commands and affect how WP-CLI interacts with WordPress.
||Path to the WordPress files.|
||Pretend request came from given URL. In multisite, this argument is how the target site is specified.|
||Perform operation against a remote server over SSH (or a container using scheme of “docker”, “docker-compose”, “docker-compose-run”, “vagrant”).|
||Perform operation against a remote WordPress installation over HTTP.|
||Set the WordPress user.|
||Skip loading all plugins, or a comma-separated list of plugins. Note: mu-plugins are still loaded.|
||Skip loading all themes, or a comma-separated list of themes.|
||Skip loading all installed packages.|
||Load PHP file before running the command (may be used more than once).|
||Execute PHP code before running the command (may be used more than once).|
||Load WordPress in a given context.|
||Whether to colorize the output.|
||Show all PHP errors and add verbosity to WP-CLI output. Built-in groups include: bootstrap, commandfactory, and help.|
||Prompt the user to enter values for all command arguments, or a subset specified as comma-separated values.|
||Suppress informational messages.|
Command documentation is regenerated at every release. To add or update an example, please submit a pull request against the corresponding part of the codebase.