im4gn.2xlarge by Amazon Web Services

im4gn.2xlarge is a Storage optimized with a one to four ratio of vCPU to memory [AWS Graviton processors] [Network and EBS optimized] Gen4 2xlarge server offered by Amazon Web Services with 8 vCPUs, 32 GiB of memory and 3.75 TB of storage. The pricing starts at 0.0802 USD per hour.
8 vCPU
32 GiB Memory
3.75 TB Storage
Spare SCore
12,132
(All-cores)
1,520
(Single-core)

Specifications

Server Metadata

Vendor ID
aws
Name
im4gn.2xlarge
Description
Storage optimized with a one to four ratio of vCPU to memory [AWS Graviton processors] [Network and EBS optimized] Gen4 2xlarge
Family
im4gn
Hw Virt
Status
active
Observed At
2026-09-06T00:31:31.376148

Availability

REGION / IDSPOTONDEMAND
Ohio (US) / us-east-2
0.134 USD/h 0.7276 USD/h
Oregon (US) / us-west-2
0.183867 USD/h 0.7276 USD/h
Northern Virgina (US) / us-east-1
0.20555 USD/h 0.7276 USD/h
Aragón (ES) / eu-south-2
0.0802 USD/h 0.8022 USD/h
Quebec (CA) / ca-central-1
0.219833 USD/h 0.8022 USD/h
Dublin (IE) / eu-west-1
0.222433 USD/h 0.8022 USD/h
Mumbai (IN) / ap-south-1
0.2668 USD/h 0.826 USD/h
Milan (IT) / eu-south-1
0.2323 USD/h 0.844 USD/h
Paris (FR) / eu-west-3
0.150033 USD/h 0.8442 USD/h
London (GB) / eu-west-2
0.235333 USD/h 0.8442 USD/h
Tokyo (JP) / ap-northeast-1
0.251433 USD/h 0.8535 USD/h
Frankfurt (DE) / eu-central-1
0.244633 USD/h 0.8675 USD/h
Sydney (AU) / ap-southeast-2
0.2047 USD/h 0.8722 USD/h
Singapore (SG) / ap-southeast-1
0.2788 USD/h 0.8722 USD/h

Processor

vCPUs
8
Hypervisor
nitro
CPU Allocation
Dedicated
CPU Cores
8
CPU Speed
2.5 GHz
CPU Architecture
arm64
CPU Manufacturer
AWS
CPU Family
ARMv8
CPU Model
Neoverse-N1
CPU L1D Cache
64 KiB
CPU L1D Cache Total
512 KiB
CPU L1I Cache
64 KiB
CPU L1I Cache Total
512 KiB
CPU L2 Cache
1 MiB
CPU L2 Cache Total
8 MiB
CPU L3 Cache
32 MiB
CPU L3 Cache Total
32 MiB
CPU Flags
fp, asimd, evtstrm, aes, pmull, sha1, sha2, crc32, atomics, fphp, asimdhp, cpuid, asimdrdm, lrcpc, dcpop, asimddp, ssbs
Ecpus
8
Scalability
100

System Resources and Accelerators

MEMORY
Memory Amount
32 GiB
Memory Amount Actual
32 GiB
GPU
GPU Count
0
GPU Memory Min
0 MiB
GPU Memory Total
0 MiB
GPUs
    STORAGE
    Storage Size
    3750 GB
    Storage Type
    nvme ssd
    Storages
    • 3750 GB nvme ssd
    NETWORK
    Network Speed Baseline
    12.5 Gbps
    Network Speed Max
    25 Gbps
    Network Storage Speed Baseline
    5 Gbps
    Network Storage Speed Max
    10 Gbps
    Inbound Traffic
    0 GB/month
    Outbound Traffic
    0 GB/month
    IPv4
    0

    Server Description

    An ARM64 storage-optimized instance featuring dense local NVMe SSD storage and balanced memory for transactional and database workloads.

    Storage & DatabaseGeneral Purpose

    Amazon Web Services im4gn.2xlarge is a storage-optimized instance featuring 8 dedicated ARM64 cores powered by AWS Graviton Neoverse-N1 processors running at 2.5 GHz. Built on the Nitro hypervisor, it includes 32.0 GB of memory and a substantial 3750 GB of local NVMe SSD storage, supported by a 12 Gbps baseline network bandwidth. Benchmark data shows average multi-core CPU performance and database operations, with Redis SET operations reaching 9.97 million operations per second. However, single-threaded performance remains a tradeoff, as reflected in weaker single-core Geekbench and compression scores. This hardware profile provides a cost-effective, resource-dense solution for storage-intensive workloads, making it highly suitable for database hosting, caching layers, and static web serving.

    Economics

    Average Price per Region

    Prices per Zone

    Lowest Prices

    Performance

    Workload Profiles

    0.567Score
    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) 967,884 ops/sec 1,917,397 ops/sec 0.505 50.00% 50.00% -28.90%
    Redis RPS (pipeline=16, SET) 5,862,624 ops/sec 11,681,410 ops/sec 0.502 20.00% 20.00% -12.90%
    PassMark Memory Mark (composite) 1,746 2,418 0.722 10.00% 10.00% -3.20%
    Memory bandwidth (read, 16 MB ~ L3) 132,334 MB/sec 108,140 MB/sec 1.22 10.00% 10.00% +2.01%
    PassMark single-thread CPU 1,110 Mops/s 2,365 Mops/s 0.469 10.00% 10.00% -7.29%

    Memory Bandwidth

    Compression

    OpenSSL

    Geekbench Single-Core

    Score: 937

    Geekbench Multi-Core

    Score: 5,430

    Passmark CPU Scores

    BENCHMARKSCORE
    Mark
    5241
    Compression
    37727
    Encryption
    1087
    Extended Instructions
    4971
    Floating Point Maths
    23964
    Integer Maths
    31579
    Physics
    1156
    Prime Numbers
    66
    Single Threaded
    1110
    String Sorting
    22940

    Passmark Memory Scores

    BENCHMARKSCORE
    Memory Mark
    1746
    Database Operations
    5226
    Memory Latency
    70
    Memory Read Cached
    9485
    Memory Read Uncached
    9220
    Memory Write
    12571

    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
    im4gn.large 28 GiB0
    im4gn.xlarge 416 GiB0
    im4gn.4xlarge 1664 GiB0
    im4gn.8xlarge 32128 GiB0
    im4gn.16xlarge 64256 GiB0

    Similar Servers

    INSTANCEVENDORvCPUsMEMORYGPUs

    im4gn.2xlarge FAQs