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 measured | Data you get | Performance impact | |
|---|---|---|---|
| Production mode | A subset of requests | An aggregated view of the system, even under load | Minimal |
| Development mode | All requests | Detailed data per request | Moderate |
| Extended script development mode | All requests | Everything development mode gives, plus the internal run-time behavior of scripts | Severe |
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.