logo

r3.2xlarge by Amazon Web Services

r3.2xlarge is a Memory optimized Gen3 2xlarge server offered by Amazon Web Services with 8 vCPUs, 61 GiB of memory and 160 GB of storage. The pricing starts at 0.1518 USD per hour.
8 vCPU
61 GiB Memory
160 GB Storage
Spare SCore
6718
(All-cores)
1286
(Single-core)

Specifications

Server Metadata

Vendor ID
aws
Name
r3.2xlarge
Description
Memory optimized Gen3 2xlarge
Family
r3
Hw Virt
Status
active
Observed At
2026-08-03T10:09:54.887586

Availability

REGION / IDSPOTONDEMAND
Ohio (US) / us-east-2
0.182633 USD/h 0.664 USD/h
Northern Virgina (US) / us-east-1
0.247675 USD/h 0.665 USD/h
Oregon (US) / us-west-2
0.237367 USD/h 0.665 USD/h
California (US) / us-west-1
0.20165 USD/h 0.741 USD/h
Dublin (IE) / eu-west-1
0.292733 USD/h 0.741 USD/h
Mumbai (IN) / ap-south-1
0.15685 USD/h 0.758 USD/h
Tokyo (JP) / ap-northeast-1
0.2147 USD/h 0.798 USD/h
Seoul (KR) / ap-northeast-2
0.2141 USD/h 0.798 USD/h
Singapore (SG) / ap-southeast-1
0.2801 USD/h 0.798 USD/h
Sydney (AU) / ap-southeast-2
0.2859 USD/h 0.798 USD/h
Frankfurt (DE) / eu-central-1
0.30725 USD/h 0.8 USD/h
Sao Paulo (BR) / sa-east-1
0.15645 USD/h 1.399 USD/h

Processor

vCPUs
8
Hypervisor
xen
CPU Allocation
Dedicated
CPU Cores
4
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
128 KiB
CPU L1I Cache
32 KiB
CPU L1I Cache Total
128 KiB
CPU L2 Cache
256 KiB
CPU L2 Cache Total
1 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, pti, fsgsbase, smep, erms, xsaveopt
Ecpus
5.2
Scalability
130

System Resources and Accelerators

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

    Server Description

    A memory-optimized virtual server featuring dedicated Intel Xeon cores, substantial RAM capacity, and integrated local NVMe SSD storage.

    Memory OptimizedStorage & Database

    Amazon Web Services r3.2xlarge is a memory-optimized instance featuring 8 vCPUs, 4 physical Intel Xeon E5-2670 v2 cores running at 2.5 GHz, and 61.0 GB of RAM. It includes 160 GB of local NVMe SSD storage and a baseline network bandwidth of 1 Gbps. Operating on the x86_64 architecture under the Xen hypervisor, the instance delivers dedicated CPU allocation. Benchmark results show average performance in multi-core CPU tests, memory bandwidth, and database operations, though single-core execution and modern vector calculations are limited due to the older processor generation and lack of AVX-512 support. The high memory-to-vCPU ratio makes this instance suitable for memory-intensive workloads, database caching, and legacy enterprise applications that require a balance of high memory capacity and local NVMe storage without demanding high single-threaded compute performance.

    Economics

    Average Price per Region

    Prices per Zone

    Lowest Prices

    Performance

    Workload Profiles

    0.358Score
    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) 559,379 ops/sec 1,910,660 ops/sec 0.293 50.00% 50.00% -45.90%
    Redis RPS (pipeline=16, SET) 2,332,780 ops/sec 11,608,287 ops/sec 0.201 20.00% 20.00% -27.40%
    PassMark Memory Mark (composite) 2,341 2,416 0.969 10.00% 10.00% -0.31%
    Memory bandwidth (read, 16 MB ~ L3) 55,081 MB/sec 107,896 MB/sec 0.511 10.00% 10.00% -6.49%
    PassMark single-thread CPU 1,880 Mops/s 2,364 Mops/s 0.795 10.00% 10.00% -2.27%

    Memory Bandwidth

    Compression

    OpenSSL

    Geekbench Single-Core

    Score: 726

    Geekbench Multi-Core

    Score: 2,768

    Passmark CPU Scores

    BENCHMARKSCORE
    Mark
    7428
    Compression
    104322
    Encryption
    3208
    Extended Instructions
    3882
    Floating Point Maths
    12632
    Integer Maths
    23019
    Physics
    915
    Prime Numbers
    46
    Single Threaded
    1880
    String Sorting
    12541

    Passmark Memory Scores

    BENCHMARKSCORE
    Memory Mark
    2341
    Database Operations
    2713
    Memory Latency
    57
    Memory Read Cached
    22837
    Memory Read Uncached
    10915
    Memory Write
    9983

    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
    r3.large 215 GiB0
    r3.xlarge 431 GiB0
    r3.4xlarge 16122 GiB0
    r3.8xlarge 32244 GiB0

    Similar Servers

    INSTANCEVENDORvCPUsMEMORYGPUs

    r3.2xlarge FAQs