You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You'll learn how to connect Codex in Visual Studio Code to the Arm Performix Model
38
+
Context Protocol (MCP) server, generate an AI insight for a specific Code Hotspots run, and
39
+
validate the result with profile evidence. After configuring the MCP server on your local machine, you’ll select or create a representative Code Hotspots run, request an AI insight by run ID, and evaluate its supporting evidence.
40
+
Then, you'll open the same run in Arm Performix to inspect flame graphs, functions, call
41
+
stacks, source, and disassembly to confirm the recommendation.
42
+
faqs:
43
+
- question: How do I confirm Codex is connected to Arm Performix through MCP?
44
+
answer: >-
45
+
Ask Codex to list Arm Performix recipes, targets, or supported Code Hotspots runs. A successful
46
+
listing confirms the MCP server is configured and reachable.
47
+
- question: Which MCP configuration method should I use, and where should I configure it?
48
+
answer: >-
49
+
You can update Codex extension settings, run the `codex mcp add` command, or
50
+
edit `~/.codex/config.toml`. Configure the MCP on the host where Codex runs; in remote development,
51
+
verify which machine hosts Codex.
52
+
- question: What should I prepare before creating a new Code Hotspots run?
53
+
answer: >-
54
+
Choose a representative workload and specify the executable with an absolute path. Build the workload with debug symbols when possible and aim for at least 20 seconds of activity to collect
55
+
enough samples.
56
+
- question: How do I make sure Codex uses the exact profile I want?
57
+
answer: >-
58
+
Request the AI Insight using the run ID. If you don’t know it, ask Codex to list supported
59
+
Code Hotspots runs with IDs, targets, workloads, and creation times. Then, select the correct
60
+
ID.
61
+
- question: What should I check to validate an AI Insight against the profile?
62
+
answer: >-
63
+
Open the same run in Arm Performix and inspect the **Flame graph**, **Functions**, **Call Stack**,
64
+
**Source**, and **Disassembly** views. Confirm that the cited functions, call paths, and sample percentages
Copy file name to clipboardExpand all lines: content/learning-paths/servers-and-cloud-computing/performix-agentic-dynamic-insights-codex/configure_mcp_codex.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -130,7 +130,7 @@ Record the run ID you want to analyze. A run name can be changed and might not b
130
130
131
131
## Troubleshoot the MCP connection
132
132
133
-
Use the following checks to diagnore MCP connection issues:
133
+
Use the following checks to diagnose MCP connection issues:
134
134
135
135
### The Arm Performix MCP server isn't listed
136
136
@@ -178,7 +178,7 @@ If you have several MCP servers, an ambiguous prompt such as `give me insights`
178
178
179
179
### Code Hotspots runs are missing
180
180
181
-
Check:
181
+
Check for the following:
182
182
183
183
- You created at least one completed Code Hotspots run.
184
184
- The MCP server runs as the same user who created or imported the run.
@@ -198,4 +198,4 @@ If the CLI also returns no run, create or import a run. If the CLI returns the r
198
198
199
199
You've now configured and tested the MCP connection.
200
200
201
-
Next, you'll create a Code Hotspots run if no supported run is available. If you already. have a supported run, skip to [Generate Arm Performix AI insights for a Code Hotspots run](/learning-paths/servers-and-cloud-computing/performix-agentic-dynamic-insights-codex/generate_ai_insights/).
201
+
Next, you'll create a Code Hotspots run if no supported run is available. If you already have a supported run, skip to [Generate Arm Performix AI insights for a Code Hotspots run](/learning-paths/servers-and-cloud-computing/performix-agentic-dynamic-insights-codex/generate_ai_insights/).
Copy file name to clipboardExpand all lines: content/learning-paths/servers-and-cloud-computing/performix-agentic-dynamic-insights-codex/create_a_code_hotspots_run.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,7 +45,7 @@ For example:
45
45
Use Arm Performix to run the Code Hotspots recipe on target "graviton-dev" with workload "/opt/myapp/bin/my_app --input /data/input.dat". Before starting, repeat the target and workload and ask me to confirm them. When the run completes, return its run ID and collection status.
46
46
```
47
47
48
-
After you confirm the target, Codex uses the MCP server to start the recipe. Review any permission request before allowing the assistant to run a command on the target.
48
+
After you confirm the target and workload, Codex uses the MCP server to start the recipe. Review any permission request before allowing the assistant to run a command on the target.
Copy file name to clipboardExpand all lines: content/learning-paths/servers-and-cloud-computing/performix-agentic-dynamic-insights-codex/open-in-performix.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,12 +11,12 @@ layout: learningpathall
11
11
12
12
A chat response helps you triage a performance problem, but the underlying profile is the source of evidence. Open the same run ID in Arm Performix and inspect the views relevant to the claim:
13
13
14
-
-**Flame graph** to see where sampled CPU time accumulates across call paths.
15
-
-**Functions** to confirm which functions account for the largest sample percentages.
16
-
-**Call Stack** to distinguish a function's own cost from the cost of its callees.
17
-
-**Source** to correlate samples with source lines when source mapping is available.
18
-
-**Disassembly** to inspect generated instructions and confirm claims about the compiled code.
19
-
-**Compare** to evaluate equivalent before-and-after runs.
14
+
-**Flame graph** to see where sampled CPU time accumulates across call paths
15
+
-**Functions** to confirm which functions account for the largest sample percentages
16
+
-**Call Stack** to distinguish a function's own cost from the cost of its callees
17
+
-**Source** to correlate samples with source lines when source mapping is available
18
+
-**Disassembly** to inspect generated instructions and confirm claims about the compiled code
19
+
-**Compare** to evaluate equivalent before-and-after runs
20
20
21
21
Use the AI insight to focus your investigation, not replace it. For example, if the insight says a loop appears scalar, inspect its disassembly and compiler flags before changing the implementation. If Code Hotspots only shows that the loop is hot, run Instruction Mix or another appropriate recipe before concluding that scalar execution is the cause.
0 commit comments