Module for debugging Magento 2 performance. It works without overwriting any core files and it can be installed with composer.

1. Enable developer mode php bin/magento deploy:mode:set developer
2. Install module via composer composer require daseraf/magento2-debug
3. Register module php bin/magento setup:upgrade
4. Enable profiler in configuration: Stores -> Configuration -> Advanced -> Debug
5. Clear cache php bin/magento c:c

For this functionality you will need to install the xhprof extension for your PHP interpreter. I recommend using PECL for these purposes. https://pecl.php.net/package/xhprof

pecl install xhprof

Just enable extension:

extension=xhprof.so

Xhprof flags are set from the Magento admin panel

Advanced -> Debug -> Data collectors -> Xhprof Flags

php bin/magento debug:db-profiler:enable

This will add a profiler flag to the database section of the env.php file

php bin/magento debug:db-profiler:disable

• Magento 2.2 - 2.4
• PHP 7.0 - 8.1

• Ajax - Please note that you can profile any requests coming into the platform, such as adding to cart
• Call map - Shows the time spent performing each function. XHprof extension required
• Database - Database queries and variable values
• Events - Displays all sent events as well as the observers tracking them
• Layout - Displays a list of blocks and the time spent on rendering them
• Layout Rendering analysis (Layout tab) - Detailed information on each block and caching status for them.

• Models - Displays loaded entity modules and the number of reloads without accessing the cache
• Plugins - Shows the plugins that were called during the process, as well as the time spent on their work. Attention - the execution time of around plugins includes the execution time of all functions that will be called in the body of the plugin. Is not an error
• Translations - here you can see all messages for which translation is missing
• Cache (Status and Calls) - This tab displays all successful cache calls (cacheKey is displayed in the table)
• Performance - here you can find a graph that is based on the output of the standard profiler from magento
• Request/Response
• Config
• Memory

• Whoops error handler

• Magento 2.x Web Profiler
• Magento 1.x Web Profiler
• Symfony WebProfilerBundle