Cert++
Close

Code Profiler modes and their performance impact

Key Takeaway

In Code Profiler, more detail costs more performance: production mode samples a subset of requests (minimal impact), development mode measures all requests (moderate impact), and extended script development mode adds script internals (severe impact).

Code Profiler is a Business Manager tool that shows how your B2C Commerce code behaves at run time, so you can find slow spots. Code Profiler has three modes, and each step up in detail costs more server performance. The core skill is picking the right mode for the detail you need and for the instance type.

The three Code Profiler modes

Code Profiler offers three modes that focus on different levels of detail. The modes differ in which requests they measure, what data you get and how much they affect performance.

Requests measuredData you getPerformance impact
Production modeA subset of requestsAn aggregated view of the system, even under loadMinimal
Development modeAll requestsDetailed data per requestModerate
Extended script development modeAll requestsEverything development mode gives, plus the internal run-time behavior of scriptsSevere

Development mode is the default mode on sandbox instances, and you can activate it on other instance types. Production mode is the default mode on non-sandbox instances, and you can't deactivate it there. All application servers in a cluster operate in the same Code Profiler mode.

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.