Arm发布面向开发者的架构优化宣传博客

As a developer, you usually start with what you’re actually building: a mobile app, cloud workload, game, or an AI feature and your immediate focus is the framework, engine, model, or service you are using.

But once that software reaches real users, something else starts to matter — the architecture it runs on. It influences how quickly your app responds, how efficiently your cloud workload runs, how smoothly your game performs, and how well your AI features behave on the device.

With 99% of smartphones running on Arm, around 50% of Arm-based compute shipped to leading hyperscalers, and more than 350 billion Arm-based chips shipped to date, the Arm architecture already powers many of the platforms developers build for every day.

So, whether you are building for cloud, games, or apps with on-device AI, your software may already run on the Arm compute platform without being deliberately optimized for it. The next step includes identifying the Arm-based device or cloud instance your workload runs on, then test its compatibility and performance in that environment.

How architecture shapes the workload

Arm’s ubiquity is reflected in an ecosystem developers already use every day: Arm-based cloud infrastructure from AWS, Google Cloud, Microsoft Azure, and Oracle Cloud Infrastructure; AI frameworks and runtimes such as LiteRT, llama.cpp, MediaPipe and ONNX Runtime; and game-development workflows involving Unreal Engine and Epic Games.

That means, once software reaches real devices and infrastructure, the architecture affects practical development outcomes such as whether the software builds and runs correctly, how efficiently it performs, what it costs to operate in the cloud, and whether performance can be sustained on a device without excessive heat, power use, or memory pressure.

This pattern is similar across various workloads:

Apps need native support, optimized libraries, profiling, and testing on representative devices.

Cloud workloads need benchmarking, dependency checks, container readiness, and configuration data.

Games need frame analysis, GPU workload visibility, memory-bandwidth checks, and sustained-performance testing.

Cloud and AI workloads

For cloud services, AI workloads, data pipelines, and performance-sensitive applications, the architecture shapes how the workload behaves across the infrastructure underneath it. Arm now reaches cloud infrastructure through a broader compute platform, from IP and Arm Compute Subsystems (CSS) used in partner-designed processors to Arm production-ready silicon, the Arm AGI CPU .

These different routes give cloud providers and system builders more ways to deploy Arm compute, while you can continue building through the operating systems, containers, libraries, and cloud services already in their workflow.

Arm-based instances are available across AWS, Google Cloud, Microsoft Azure, and Oracle Cloud Infrastructure, giving you a route to Arm across leading cloud environments. If you are starting a new service or migrating an existing workload, the next practical steps are to assess dependencies and container readiness, build a multi-architecture environment, and validate performance on the infrastructure you plan to use.

Migration tools can help identify compatibility issues and prepare CI/CD workflows. Once running, benchmarking tools such as Arm Performix can help provide insights into hotspots, memory usage, and CPU efficiency to guide optimization.

Games and graphics

For games and real-time 3D experiences, many players are likely to already be using Arm-powered smartphones, tablets, or gaming platforms. In those environments, performance depends on how frame rates, responsiveness, visual quality, heat, battery life, and sustained gameplay come together.

That makes mobile game performance optimization and profiling central to the development process. Frame pacing, thermal behavior, memory bandwidth, GPU workload, and longer-session performance all help connect what happens inside the game engine to what players experience on the device.

Developers can begin exploring these workflows through the open Arm Neural Graphics Development Kit , which includes Unreal Engine plugins, Vulkan ML tools, models, code samples, profiling tools, and technical guidance.

Neural graphics can improve visual quality and frame rates while reducing the rendering work needed to produce each frame. Techniques such as neural upscaling, denoising, and frame generation make it possible to create richer scenes and smoother experiences within mobile power and thermal limits.

Arm Neural Technology brings these capabilities into mobile graphics workflows, while Neural Dawn – created by Arm and Sumo Digital using Unreal Engine – shows them working in a production-quality game with MegaLights, ray-traced effects, and high-quality frame delivery.

Apps and on-device AI

For apps, architecture is most visible in everyday interactions. It affects how quickly an app opens, how responsive it feels, how long the device lasts, and how fast AI-enabled features return a result. As apps add more on-device AI features for language, vision, voice, and image workloads, running AI efficiently on the CPU becomes an important part of the user experience.

This is because you can improve the speed and responsiveness of AI features through the models, frameworks, and runtimes you already use. On supported Armv9 devices, Arm Scalable Matrix Extension 2 (Arm SME2) accelerates the matrix-heavy operations behind language, vision, speech, and image workloads directly on the CPU, further helping reduce latency and power use.

Through Arm KleidiAI and integrations with XNNPACK, LiteRT, llama.cpp, MediaPipe, MNN, and ONNX Runtime, supported workloads can access SME2 acceleration through familiar software stacks.

Start with where you’re targeting

If you are building cloud and AI workloads, games and graphics, or apps with on-device AI, Arm developer resources bring together the tools, learning paths, technical guides, and libraries that help you move from understanding the architecture to using it in your own workflow.

The Arm Developer Program also offers a broader entry point into the resources, technical guidance, and community available to developers building on Arm.

If your users are on smartphones, cloud services, games, laptops, connected devices, or AI-enabled platforms, Arm is likely to be part of your software story. So, when you understand that connection, you can build, optimize, and scale easier and faster.

What are you targeting?

Choose the path closest to what you are working on and get to the Arm tools, learning paths, libraries, and technical guidance that fit your workflow.

Learn more

The post Your users are already on Arm – is your software targeting it? appeared first on Arm Newsroom .