Using Code Profiler

The Code Profiler provides insights into run-time performance. There are three levels of detail:

  1. Open the storefront for the site you want to examine.
  2. Select Administration > Operations > Code Profiler.
  3. Select the mode.
    • Production Mode
    • Development Mode
    • Extended Script Development Mode
      Note: When you change modes, the results are flushed. If you are gathering data on a sandbox, you need to make the behavior occur again to measure it. However, if you are gathering data on a production instance that has sufficient traffic, you might simply have to wait to see the behavior.
  4. To change what appears in the results, specify the result types to view.
    Option Description
    Result Type Includes
    Request
    • ONREQUEST: onrequest calls
    • REST_SHOP: OCAP Shop API requests
    • REST_DATA: OCAPI Data API requests
    • REST_BATCH: OCAPI Batch API requests
    • REST_META: OCAPI Meta API results
    • SF_PAGE: storefront page requests
    Job
    • JOB: Job execution
    • JOB_STEP: Job steps
    Controller
    • SCRIPT_CONTROLLER: JavaScript controllers
    • PIPELINE: pipelines
    • PIPELINE_NODE: individual pipeline nodes, such as pipelets
    • SCRIPT_PIPELET: script pipelets
    Script details
    • SCRIPT_API: API call
    • SCRIPT_FUNCTION: JavaScript functions
    • SCRIPT_HOOK: Hook function
    • SCRIPT_LINE: single lines of JavaScript code
    View
    • ISML template rendering
  5. To remove results for a result type, uncheck the box next to the filter and click Apply.
  6. To add result types, check the box next to the filter and click Apply.
  7. To sort the results table, click a column heading.