m9gd.12xlarge by Amazon Web Services

m9gd.12xlarge is a General purpose [AWS Graviton processors] [Instance store volumes] Gen9 12xlarge server offered by Amazon Web Services with 48 vCPUs, 192 GiB of memory and 2.85 TB of storage. The pricing starts at 0.4541 USD per hour.
48 vCPU
192 GiB Memory
2.85 TB Storage
Spare SCore
96,247
(All-cores)
2,010
(Single-core)

Specifications

Server Metadata

Vendor ID
aws
Name
m9gd.12xlarge
Description
General purpose [AWS Graviton processors] [Instance store volumes] Gen9 12xlarge
Family
m9gd
Hw Virt
Average Time To Start
17.5
Status
active
Observed At
2026-09-09T06:57:48.483571

Availability

REGION / IDSPOTONDEMAND
Northern Virgina (US) / us-east-1
0.64785 USD/h 3.0168 USD/h
Ohio (US) / us-east-2
0.7084 USD/h 3.0168 USD/h
Oregon (US) / us-west-2
1.009675 USD/h 3.0168 USD/h
Dublin (IE) / eu-west-1
1.550933 USD/h 3.3643 USD/h
Frankfurt (DE) / eu-central-1
1.166267 USD/h 3.6312 USD/h
Singapore (SG) / ap-southeast-1
1.347733 USD/h 3.7646 USD/h
Sydney (AU) / ap-southeast-2
1.3525 USD/h 3.791 USD/h
Tokyo (JP) / ap-northeast-1
1.465467 USD/h 3.8976 USD/h

Processor

vCPUs
48
Hypervisor
nitro
CPU Allocation
Dedicated
CPU Cores
48
CPU Speed
3.3 GHz
CPU Architecture
arm64
CPU Manufacturer
AWS
CPU Family
ARMv9
CPU Model
Neoverse-V3
CPU L1D Cache
64 KiB
CPU L1D Cache Total
3 MiB
CPU L1I Cache
64 KiB
CPU L1I Cache Total
3 MiB
CPU L2 Cache
2 MiB
CPU L2 Cache Total
96 MiB
CPU L3 Cache
48 MiB
CPU L3 Cache Total
48 MiB
CPU Flags
fp, asimd, evtstrm, aes, pmull, sha1, sha2, crc32, atomics, fphp, asimdhp, cpuid, asimdrdm, jscvt, fcma, lrcpc, dcpop, sha3, asimddp, sha512, sve, asimdfhm, dit, uscat, ilrcpc, flagm, sb, paca, pacg, dcpodp, sve2, sveaes, svepmull, svebitperm, svesha3, flagm2, frint, svei8mm, svebf16, i8mm, bf16, dgh, rng, bti, ecv, afp, wfxt
Ecpus
47.9
Scalability
99.79

System Resources and Accelerators

MEMORY
Memory Amount
192 GiB
Memory Amount Actual
189 GiB
GPU
GPU Count
0
GPU Memory Min
0 MiB
GPU Memory Total
0 MiB
GPUs
    STORAGE
    Storage Size
    2850 GB
    Storage Type
    nvme ssd
    Storages
    • 950 GB nvme ssd
    • 950 GB nvme ssd
    • 950 GB nvme ssd
    NETWORK
    Network Speed Baseline
    25 Gbps
    Network Speed Max
    25 Gbps
    Network Storage Speed Baseline
    18 Gbps
    Network Storage Speed Max
    18 Gbps
    Inbound Traffic
    0 GB/month
    Outbound Traffic
    0 GB/month
    IPv4
    0

    CPU and System Topology

    Server Description

    A balanced ARMv9 platform featuring dedicated compute cores, high-speed local NVMe storage, and top-tier database and memory performance.

    General PurposeStorage & Database

    Amazon Web Services m9gd.12xlarge is a general-purpose server powered by a 3.3 GHz AWS Graviton ARMv9 Neoverse-V3 processor with 48 dedicated physical cores and 192.0 GB of system memory. It features 2850 GB of local NVMe SSD storage and a baseline network bandwidth of 25 Gbps. Benchmark results show top-tier performance in software compilation, database operations, Redis SET operations, and static web serving. While single-core and multi-core Geekbench scores are in the top 10%, text generation for small language models is a relative bottleneck. This instance provides a cost-efficient hardware profile for workloads requiring high-speed local storage and balanced compute resources, making it suitable for database hosting, web serving, and CI/CD compilation pipelines.

    Economics

    Average Price per Region

    Prices per Zone

    Lowest Prices

    Performance

    Workload Profiles

    5.24Score
    Precomputed compound score for Cache Intensive workloads. A weighted average (geometric mean) of benchmark scores compared to their medians: score = ∏ (x_i / m_i)^(w_i / Σw). The score of 1.0 represents a synthetic baseline server with the median performance of each component benchmark; 0.5 means roughly half the performance; and 2.0 means twice the performance of that reference profile. Component weights: 50% Redis RPS (pipeline=1, SET), 20% Redis RPS (pipeline=16, SET), 10% PassMark Memory Mark (composite), 10% Memory bandwidth (read, 16 MB ~ L3), 10% PassMark single-thread CPU. Rationale for component selection: In-memory key-value store workload, mixing direct Redis performance metrics with memory speed and latency benchmarks, and single-core CPU performance profiles.
    Component Score Weight Impact
    Raw Reference Normalized Target Actual
    Redis RPS (pipeline=1, SET) 16,911,029 ops/sec 1,917,397 ops/sec 8.82 50.00% 50.00% +197.00%
    Redis RPS (pipeline=16, SET) 98,690,026 ops/sec 11,681,410 ops/sec 8.45 20.00% 20.00% +53.20%
    PassMark Memory Mark (composite) 4,658 2,418 1.93 10.00% 10.00% +6.80%
    Memory bandwidth (read, 16 MB ~ L3) 218,782 MB/sec 108,140 MB/sec 2.02 10.00% 10.00% +7.28%
    PassMark single-thread CPU 2,468 Mops/s 2,365 Mops/s 1.04 10.00% 10.00% +0.39%

    Memory Bandwidth

    Compression

    OpenSSL

    Geekbench Single-Core

    Score: 2,396

    Geekbench Multi-Core

    Score: 28,199

    Passmark CPU Scores

    BENCHMARKSCORE
    Mark
    		 49413
    Compression
    		 448163
    Encryption
    		 14327
    Extended Instructions
    		 64637
    Floating Point Maths
    		 367360
    Integer Maths
    		 293877
    Physics
    		 10681
    Prime Numbers
    		 589
    Single Threaded
    		 2468
    String Sorting
    		 247364

    Passmark Memory Scores

    BENCHMARKSCORE
    Memory Mark
    		 4658
    Database Operations
    		 46542
    Memory Latency
    		 27
    Memory Read Cached
    		 24911
    Memory Read Uncached
    		 24689
    Memory Write
    		 24941

    Stress-ng Raw Scores

    Stress-ng Relative Multicore Performance

    LLM Inference Speed for Prompt Processing

    LLM Inference Speed for Text Generation

    Static Web Server

    Redis

    Alternatives

    Servers of the Same Family

    INSTANCEvCPUsMEMORYGPUs
    m9gd.medium 14 GiB0
    m9gd.large 28 GiB0
    m9gd.xlarge 416 GiB0
    m9gd.2xlarge 832 GiB0
    m9gd.4xlarge 1664 GiB0
    m9gd.8xlarge 32128 GiB0
    m9gd.16xlarge 64256 GiB0

    Similar Servers

    INSTANCEVENDORvCPUsMEMORYGPUs

    m9gd.12xlarge FAQs