If you have an execution plan and want to understand the meaning and cost composition of each operator, you can submit the execution plan to the Agent for interpretation operator by operator.
When to use
You have obtained an execution plan from OCP, OAS, or a client, but are unclear about the specific meaning of each operator.
You need to determine which part of the execution plan is a performance bottleneck.
You want to compare two execution plans before and after optimization to confirm whether the optimization took effect.
Prerequisites
You have obtained the execution plan content (exported from the OCP or OAS console, or copied from the client).
If you need to upload the execution plan file as an attachment, please understand the upload operation. For details, see Upload an attachment.
Procedure
Paste the execution plan content into the session, or upload the execution plan file as an attachment.
Describe your interpretation request, for example:
Help me interpret this execution plan and identify the bottleneck.Press Enter to send it, and wait for the Agent to complete the interpretation.
View the interpretation result.
The Agent will explain the following content operator by operator and identify potential performance bottleneck parts in the plan:
Interpretation dimensionDescriptionScan method Whether the operator uses full table scan, index scan, or primary key scan. Join method The algorithm used for table joins (such as Nested Loop Join, Hash Join, Merge Join) and the selection of the driving table. Cost estimation The estimated number of rows and cost for each operator, and the deviation between the estimated and actual values.
Usage suggestions
- When pasting the execution plan, retain the complete operator tree and cost columns. Missing columns will affect the accuracy of the interpretation.
What to do next
If the estimated number of rows deviates significantly from the actual number of rows, it usually indicates that the statistics are outdated. You can proceed with statistics diagnostics. For details, see Statistics diagnostics.
To assess the execution plan risk of a new SQL statement or obtain tuning suggestions, see SQL pre-analysis and tuning suggestions.
To export the interpretation results to a report, see Export a report.