start_profiling
June 8, 2026 ยท View on GitHub
Start performance measurement on the active debug target. Enables line-level profiling: call counts and timing for every executed BSL line. Start-only and idempotent: if profiling is already active for this applicationId it stays on. Call stop_profiling to stop, then get_profiling_results to see which code was covered. Requires an active debug session (debug_launch or debug_yaxunit_tests).
Parameters
| Parameter | Required | Type | Description |
|---|---|---|---|
| applicationId | yes | string | Application id of the running debug session (required) |
Guide
Turns on 1C line-level performance measurement for a running debug session: once active, every executed BSL line is tracked with its call count and timing. Run your scenario, then stop_profiling and get_profiling_results to see what code ran and where the time went (also doubles as code-coverage).
When to use
- You want to know which lines actually execute during a scenario, or where the time goes.
- Measuring coverage of a YAXUnit run or a manual test (start it, exercise the code, stop, read results).
Parameter details
applicationId(required) - the running debug session to profile. Get it fromget_applicationsordebug_status; adebug_yaxunit_tests/debug_launchrun provides one.
What you get
JSON: active, started (true if this call switched it on, false if it was already on), applicationId, and a message with the next step.
Notes & gotchas
- Requires an active DEBUG session - start one with
debug_launchordebug_yaxunit_testsfirst. A plain run is not enough. - Start-only and idempotent: calling it again while already profiling does NOT toggle it off - it reports "already active". (The on/off state is shared with
stop_profiling.) - The data is collected on the debug server while the session runs; you only see it after
stop_profiling+get_profiling_results.
Generated from the live MCP server (get_tool_guide) by docs/generate_tool_docs.py. Do not edit this file. Edit the tool's description/schema in its Java source and its guide body in mcp/bundles/com.ditrix.edt.mcp.server/guides/<tool>.md.