Cert++
Close

Choosing a performance tool and isolating server versus client slowness

Key Takeaway

First find out whether the time goes to the server or to the client, then pick a tool for that side. For a slow production instance where you don't know which application server handles the slow requests, use Code Profiler in Production mode, because it measures a subset of requests on all application servers in the cluster with minimal impact.

When a B2C Commerce storefront is slow, start by finding where the time goes. The time is spent either on the server (controllers, scripts, templates and page cache) or on the client side (the network and the browser). Server-side tools live in Business Manager and B2C Commerce Reports & Dashboards. Browser-based tools cover the client side. So the right tool depends on which side you suspect and what kind of data you need.

Server tools and client tools

Profiling tools are either server-based or client-based. Each side has its own performance concerns.

Server tools include the Technical Reports dashboard in B2C Commerce Reports & Dashboards, Code Profiler and Pipeline Profiler. Google Lighthouse is a client tool.

B2C Commerce Developer Study Guide

Checklist progress

0/237Learned

Given a problem or performance issue and data, use relevant tools to inspect code performance and determine and implement solutions (cache configuration, profilers, etc.) to resolve this issue

0/11

Prepare for the Exam

Play Today's Certle

Study Community

Ask questions and get the latest info from other B2C Commerce Developer studiers. 796 members and growing.