This repository provides technical guidance for users and developers using Amazon EC2 instances powered by AWS Graviton processors (including the latest generation Graviton4 processors). While it calls out specific features of the Graviton processors themselves, this repository is also generally useful for anyone running code on Arm-based systems.

• Transitioning to Graviton
• Building for Graviton
• Optimizing for Graviton
• Taking advantage of Arm Advanced SIMD instructions
• Recent software updates relevant to Graviton
• Language-specific considerations
  • C/C++
  • Go
  • Java
  • .NET
  • Node.JS
  • PHP
  • Python
  • Rust
• Containers on Graviton
• Headless website testing with Chrome and Puppeteer on Graviton
• Lambda on Graviton
• Operating Systems support
• Third-party Software Vendors
• Finding and managing AMIs for Graviton, with AWS SystemManager or CloudFormation
• DPDK, SPDK, and other datapath software
• PyTorch
• llama.cpp
• R
• TensorFlow
• Spark on Graviton
• Known issues and workarounds
• AWS Managed Services available on Graviton
• Graviton Performance Runbook
• Assembly Optimization Guide for Graviton Arm64 Processors
• Additional resources
• How To Resources
• Blog Posts
• Case Studies

If you are new to Graviton and want to understand how to identify target workloads, how to plan a transition project, how to test your workloads on AWS Graviton and finally how deploy in production, please read the key considerations to take into account when transitioning workloads to AWS Graviton based Amazon EC2 instances.

Please refer to optimizing for general debugging and profiling information. For detailed checklists on optimizing and debugging performance on Graviton, see our performance runbook.

Different architectures and systems have differing capabilities, which means some tools you might be familiar with on one architecture don't have equivalent on AWS Graviton. Documented Monitoring Tools with some of these utilities.

There is a huge amount of activity in the Arm software ecosystem and improvements are being made on a daily basis. As a general rule later versions of compilers, language runtimes, and applications should be used whenever possible. The table below includes known recent changes to popular packages that improve performance (if you know of others please let us know).

You can run Docker, Kubernetes, Amazon ECS, and Amazon EKS on Graviton. Amazon ECR supports multi-arch containers. Please refer to containers for information about running container-based workloads on Graviton.

AWS Lambda now allows you to configure new and existing functions to run on Arm-based AWS Graviton2 processors in addition to x86-based functions. Using this processor architecture option allows you to get up to 34% better price performance. Duration charges are 20 percent lower than the current pricing for x86 with millisecond granularity. This also applies to duration charges when using Provisioned Concurrency. Compute Savings Plans supports Lambda functions powered by Graviton2.

The Lambda page highlights some of the migration considerations and also provides some simple to deploy demos you can use to explore how to build and migrate to Lambda functions using Arm/Graviton2.

Please check os.md for more information about which operating system to run on Graviton based instances.

Postgres performance can be heavily impacted by not using LSE. Today, postgres binaries from distributions (e.g. Ubuntu) are not built with -moutline-atomics or -march=armv8.2-a which would enable LSE. Note: Amazon RDS for PostgreSQL isn't impacted by this.

In November 2021 PostgreSQL started to distribute Ubuntu 20.04 packages optimized with -moutline-atomics. For Ubuntu 20.04, we recommend using the PostgreSQL PPA instead of the packages distributed by Ubuntu Focal. Please follow the instructions to set up the PostgreSQL PPA.

The default installation of pip on some Linux distributions is old (<19.3) to install binary wheel packages released for Graviton. To work around this, it is recommended to upgrade your pip installation using:

sudo python3 -m pip install --upgrade pip

The Bazel build tool now releases a pre-built binary for arm64. As of October 2020, this is not available in their custom Debian repo, and Bazel does not officially provide an RPM. Instead, we recommend using the Bazelisk installer, which will replace your bazel command and keep bazel up to date.

Below is an example using the latest Arm binary release of Bazelisk as of October 2020:

wget https://github.com/bazelbuild/bazelisk/releases/download/v1.7.1/bazelisk-linux-arm64
chmod +x bazelisk-linux-arm64
sudo mv bazelisk-linux-arm64 /usr/local/bin/bazel
bazel

Bazelisk itself should not require further updates, as its only purpose is to keep Bazel updated.

Linux distributions, in general, use the original zlib without any optimizations. zlib-cloudflare has been updated to provide better and faster compression on Arm and x86. To use zlib-cloudflare:

git clone https://github.com/cloudflare/zlib.git
cd zlib
./configure --prefix=$HOME
make
make install

Make sure to have the full path to your lib at $HOME/lib in /etc/ld.so.conf and run ldconfig.

For users of OpenJDK, which is dynamically linked to the system zlib, you can set LD_LIBRARY_PATH to point to the directory where your newly built version of zlib-cloudflare is located or load that library with LD_PRELOAD.

You can check the libz that JDK is dynamically linked against with:

$ ldd /Java/jdk-11.0.8/lib/libzip.so | grep libz
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007ffff7783000)

Currently, users of Amazon Corretto cannot link against zlib-cloudflare.

• Application deep-dive into the AWS Graviton3E-based Amazon EC2 Hpc7g instance
• Rescale Automates the Deployment of Ansys LS-DYNA and Ansys Fluent Workloads on Amazon EC2 Hpc7g Instances
• Lattice Boltzmann simulation with Palabos on AWS using Graviton-based Amazon EC2 Hpc7g instances
• Instance sizes in the Amazon EC2 Hpc7 family – a different experience
• Checkpointing HPC applications using the Spot Instance two-minute notification from Amazon EC2
• Best practices for running molecular dynamics simulations on AWS Graviton3E

• Optimized PyTorch 2.0 inference with AWS Graviton processors
• Reduce Amazon SageMaker inference cost with AWS Graviton
• PyTorch blog: Optimized PyTorch 2.0 Inference with AWS Graviton processors
• PyTorch Inference Performance Tuning on AWS Graviton Processors
• PyTorch blog: Accelerated PyTorch inference with torch.compile on AWS Graviton processors
• Sprinklr improves performance by 20% and reduces cost by 25% for machine learning inference on AWS Graviton3
• Run machine learning inference workloads on AWS Graviton-based instances with Amazon SageMaker
• Accelerate NLP inference with ONNX Runtime on AWS Graviton processors
• Best-in-class LLM Performance on Arm Neoverse V1 based AWS Graviton3 CPUs
• Accelerating Popular Hugging Face Models using Arm Neoverse
• Run LLMs on CPU with Amazon SageMaker Real-time Inference
• Accelerating large-scale neural network training on CPUs with ThirdAI and AWS Graviton
• Enhancing LLM Serving with Torch Compiled RAG on AWS Graviton
• Intro to Llama on Graviton

• Optimized Video Encoding with FFmpeg on AWS Graviton Processors

• Encored Technologies Successfully Built an HPC on AWS for Weather Research & Forecasting (WRF)
• Arm Scales Performance for Chip Design Using Amazon FSx for NetApp ONTAP
• The Institut Pasteur and AWS are analysing the world's DNA, using a public database

• Lower Latency and Costs Using AWS Graviton2–Based Instances with Sprinklr

• AWS Graviton
• Neoverse N1 Software Optimization Guide
• Armv8 reference manual
• Package repository search tool

Feedback? [email protected]