apex-debug-performance
Investigate Apex performance
Find relevant executions across the corpus before profiling individual files. Correct and verify when requested, distinguishing measurements from hypotheses.
Select executions
For current org activity run sf electivus doctor --target-org my-org --json and sf electivus log sync --target-org my-org --json in the workspace. Check the inner sync result for partial failure even when outer status is zero. Use orgLogsRoot; older plugins expose apexlogsRoot and safeTargetOrg through log status. Check public help for unfamiliar capabilities.
For supplied/offline logs start directly with those paths, without org access or software installation. Reuse the corpus across searches; subsequent syncs collect new reproduction activity. Use --force-full for retained history missing behind the checkpoint, not routine searches.
rg --no-ignore -l -F -g '*.log' -- 'CheckoutService' '/absolute/orgLogsRoot'
rg --no-ignore -n -C 3 -e 'LIMIT_USAGE_FOR_NS|CUMULATIVE_LIMIT_USAGE|FATAL_ERROR' -- '/absolute/path/candidate.log'
The corpus is normally gitignored, so use --no-ignore. Find filenames before printing content. Read references/performance.md for legacy scoping, capture requirements and comparison.