Magento 2 profiling

Backend related performance issues can be hard to track down.

Luckily, Magento 2 comes with its own profiler to help you do this.

The built-in profiler should always be used on a Staging account since it has an impact on performance and adds debugging information to the frontend.

Below are the steps to enable the profiler and track down issues:

1. Make sure your code on Staging is in sync with production
    
2. Make sure your database on Staging is in sync with production
    
3. Reproduce the issue on staging. To make sure you don't hit Varnish add `?no_cache=1` to the URL.
    
4. Go to the Magento 2 directory and run:

   bin/magento dev:profiler:enable html

      
5. Hit the page where the problem persists again
   1. Scroll to the bottom of the page
   2. Find the element with the highest value in the 'Time' column
   3. You will now have a good indication where the most time is spent
      
      
6. To disable: Go to the Magento 2 directory and run:

   bin/magento dev:profiler:disable