i2.4xlarge by Amazon Web Services

i2.4xlarge is a Storage optimized Gen2 4xlarge server offered by Amazon Web Services with 16 vCPUs, 122 GiB of memory and 3.2 TB of storage. The pricing starts at 0.341 USD per hour.
16 vCPU
122 GiB Memory
3.2 TB Storage
Spare SCore
14,126
(All-cores)
1,623
(Single-core)

Specifications

Server Metadata

Vendor ID
aws
Name
i2.4xlarge
Description
Storage optimized Gen2 4xlarge
Family
i2
Hw Virt
Status
active
Observed At
2026-09-22T13:30:20.188901Z

Availability

REGION / IDSPOTONDEMAND
Ohio (US) / us-east-2
0.341 USD/h 3.41 USD/h
Oregon (US) / us-west-2
0.701733 USD/h 3.41 USD/h
Northern Virgina (US) / us-east-1
0.8441 USD/h 3.41 USD/h
California (US) / us-west-1
0.4471 USD/h 3.751 USD/h
Dublin (IE) / eu-west-1
0.987633 USD/h 3.751 USD/h
Mumbai (IN) / ap-south-1
0.5578 USD/h 3.867 USD/h
Seoul (KR) / ap-northeast-2
0.6124 USD/h 4.002 USD/h
Tokyo (JP) / ap-northeast-1
0.7078 USD/h 4.002 USD/h
Frankfurt (DE) / eu-central-1
0.7437 USD/h 4.051 USD/h
Sydney (AU) / ap-southeast-2
0.837967 USD/h 4.07 USD/h
Singapore (SG) / ap-southeast-1
0.8146 USD/h 4.07 USD/h

Processor

vCPUs
16
Hypervisor
xen
CPU Allocation
Dedicated
CPU Cores
8
CPU Speed
2.5 GHz
CPU Architecture
x86_64
CPU Manufacturer
Intel
CPU Family
Xeon
CPU Model
E5-2670 v2
CPU L1D Cache
32 KiB
CPU L1D Cache Total
256 KiB
CPU L1I Cache
32 KiB
CPU L1I Cache Total
256 KiB
CPU L2 Cache
256 KiB
CPU L2 Cache Total
2 MiB
CPU L3 Cache
25 MiB
CPU L3 Cache Total
25 MiB
CPU Flags
fpu, vme, de, pse, tsc, msr, pae, mce, cx8, apic, sep, mtrr, pge, mca, cmov, pat, pse36, clflush, mmx, fxsr, sse, sse2, ht, syscall, nx, rdtscp, lm, constant_tsc, rep_good, nopl, xtopology, cpuid, tsc_known_freq, pni, pclmulqdq, ssse3, cx16, pcid, sse4_1, sse4_2, x2apic, popcnt, tsc_deadline_timer, aes, xsave, avx, f16c, rdrand, hypervisor, lahf_lm, cpuid_fault, pti, fsgsbase, smep, erms, xsaveopt
Ecpus
8.7
Scalability
54.37

System Resources and Accelerators

MEMORY
Memory Amount
122 GiB
Memory Amount Actual
122 GiB
GPU
GPU Count
0
GPU Memory Min
0 MiB
GPU Memory Total
0 MiB
GPUs
    STORAGE
    Storage Size
    3200 GB
    Storage Type
    nvme ssd
    Storages
    • 800 GB nvme ssd
    • 800 GB nvme ssd
    • 800 GB nvme ssd
    • 800 GB nvme ssd
    NETWORK
    Network Speed Baseline
    2 Gbps
    Network Speed Max
    10 Gbps
    Network Storage Speed Baseline
    2 Gbps
    Network Storage Speed Max
    2 Gbps
    Inbound Traffic
    0 GB/month
    Outbound Traffic
    0 GB/month
    IPv4
    0

    Server Description

    A storage-optimized virtual server featuring substantial local NVMe SSD capacity and balanced memory for database and static web serving workloads.

    Storage & DatabaseMemory Optimized

    Amazon Web Services i2.4xlarge is a storage-optimized instance utilizing the Xen hypervisor and x86_64 architecture. It is configured with an Intel Xeon E5-2670 v2 processor offering 16 vCPUs, 8 physical cores, and a 2.5 GHz clock speed. The hardware profile includes 122.0 GB of RAM and a bundled 3200 GB NVMe SSD for high-capacity local storage, supported by a 2 Gbps baseline network bandwidth. Benchmark data indicates average performance in multi-core CPU tests and database operations, though single-core execution and memory write speeds are relatively weak. Qualitatively, the instance provides high local storage density, making it a viable option for legacy database hosting, static web serving, and storage-heavy applications. However, its older processor architecture makes it less efficient for modern compute-intensive workloads or machine learning inference.

    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) 1,213,366 ops/sec 2,031,101 ops/sec 0.597 50.00% 50.00% -22.70%
    Redis RPS (pipeline=16, SET) 4,858,638 ops/sec 12,409,308 ops/sec 0.392 20.00% 20.00% -17.10%
    PassMark Memory Mark (composite) 2,116 2,418 0.875 10.00% 10.00% -1.33%
    Memory bandwidth (read, 16 MB ~ L3) 43,160 MB/sec 108,315 MB/sec 0.398 10.00% 10.00% -8.80%
    PassMark single-thread CPU 1,991 Mops/s 2,365 Mops/s 0.842 10.00% 10.00% -1.71%

    Memory Bandwidth

    Compression

    OpenSSL

    Geekbench Single-Core

    Score: 532

    Geekbench Multi-Core

    Score: 3,448

    Passmark CPU Scores

    BENCHMARKSCORE
    Mark
    16684
    Compression
    232065
    Encryption
    7439
    Extended Instructions
    9237
    Floating Point Maths
    31157
    Integer Maths
    58276
    Physics
    2040
    Prime Numbers
    118
    Single Threaded
    1991
    String Sorting
    32310

    Passmark Memory Scores

    BENCHMARKSCORE
    Memory Mark
    2116
    Database Operations
    6516
    Memory Latency
    72
    Memory Read Cached
    20203
    Memory Read Uncached
    9645
    Memory Write
    8731

    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
    i2.xlarge 431 GiB0
    i2.2xlarge 861 GiB0
    i2.8xlarge 32244 GiB0

    Similar Servers

    INSTANCEVENDORvCPUsMEMORYGPUs

    i2.4xlarge FAQs