Generate Arm Performix AI insights in Visual Studio Code with Codex
Introduction
Understand the AI-assisted Arm Performix insight workflow
Configure the Arm Performix MCP server in Codex
Create an Arm Performix Code Hotspots run
Generate Arm Performix AI insights for a Code Hotspots run
Open the run in Arm Performix for deeper inspection
Next Steps
Generate Arm Performix AI insights in Visual Studio Code with Codex
Arm Performix MCP server
Arm Performix is a performance toolkit designed to help developers identify bottlenecks and validate improvements on Arm-based systems. The toolkit turns low-level performance data into actionable insights through guided analysis paths called recipes. You can use these recipes to answer common performance questions and move quickly from observation to root cause.
Arm Performix includes a local Model Context Protocol (MCP) server. MCP is a standard way for an AI assistant to discover and call tools. AI assistants such as Codex can use the server to query Performix recipes, targets, and runs from Visual Studio Code (VS Code) instead of relying on source-code analysis alone.
You’ll connect the server to Codex, select or create a Code Hotspots run, and ask for an AI insight. The response should connect each recommendation to evidence from the selected run.
The MCP server runs on the same host as Codex. It can make profile data, symbols, source excerpts, disassembly excerpts, and performance metrics available to the assistant. Before you continue, confirm that this use complies with your organization’s data-handling policy.
Use AI-generated responses to support performance investigation. Validate important findings by reviewing the relevant data in Arm Performix and by rerunning the workload after making changes.
How AI-assisted Arm Performix insights are generated
Arm Performix stores profiling runs, target information, and rendered analysis data. The local MCP server exposes specific Performix capabilities as tools that an MCP-compatible assistant can call.
When you ask for insights, the flow is:
- You ask an AI assistant — in this case, Codex in VS Code — for an Arm Performix insight.
- Codex calls the Arm Performix MCP server.
- Arm Performix gathers relevant run data and profile evidence.
- Codex uses that evidence to identify likely bottlenecks, explain why they matter, and suggest the next investigation step.
The available evidence depends on how the run was collected. Debug symbols and source mappings improve function and source-line attribution, while a representative profiling duration improves sampling quality.
What you’ve learned and what’s next
You’ve learned about Arm Performix’s local MCP server and how AI-assisted insights are generated.
Next, you’ll configure the local MCP server and verify that Codex can use its tools.