AWS

r3.xlarge

EC2 Instance

About the

r3.xlarge

instance

Previous generation memory-optimized instance with 4 vCPUs, 30.5 GiB memory, and 1x80GB SSD. Good for medium-sized in-memory databases and enterprise applications.

Coming Soon...

Pricing of

r3.xlarge

N/A

On Demand

N/A

Spot

N/A

1 Yr Reserved

N/A

3 Yr Reserved

Let us help you choose the right instance

Schedule a meeting

Spot Pricing Details for

r3.xlarge

Here's the latest prices for this instance across this region:

Availability Zone	Current Spot Price (USD)

Frequency of Interruptions: n/a

Frequency of interruption represents the rate at which Spot has reclaimed capacity during the trailing month. They are in ranges of < 5%, 5-10%, 10-15%, 15-20% and >20%.

Last Updated On: December 17, 2024

Compute features of

r3.xlarge

Feature	Specification

Storage features of

r3.xlarge

Feature	Specification

Networking features of

r3.xlarge

Feature	Specification

Operating Systems Supported by

r3.xlarge

Operating System	Supported

Security features of

r3.xlarge

Feature	Supported

General Information about

r3.xlarge

Feature	Specification

Benchmark Test Results for

r3.xlarge

CPU Encryption Speed Benchmarks

Cloud Mercato tested CPU performance using a range of encryption speed tests:

Encryption Algorithm	Speed (1024 Block Size, 3 threads)
AES-128 CBC	N/A
AES-256 CBC	N/A
MD5	N/A
SHA256	N/A
SHA512	N/A

I/O Performance

Cloud Mercato's tested the I/O performance of this instance using a 100GB General Purpose SSD. Below are the results:

	Read	Write
Max	N/A	N/A
Average	N/A	N/A
Deviation	N/A	N/A
Min	N/A	N/A

I/O rate testing is conducted with local and block storages attached to the instance. Cloud Mercato uses the well-known open-source tool FIO. To express IOPS the following parametersare used: 4K block, random access, no filesystem (except for write access with root volume and avoidance of cache and buffer.

See

Cloud Mercato's full benchmark results for this instance here

Community Insights for

r3.xlarge

AI-summarized insights

Filter by:

All

I use the AWS EKS Quickstart to launch a cluster I select "t4g.small" or "m6gd.xlarge" as the instance type and "General" as the instance family. But it looks like that is incorrect, is it supposed to be "ARM"? isn't it?

24-11-2021

Read original

If you have an Amazon EC2 instance that is **used infrequently** , then the best way to save money is to **stop the instance**.

2017-01-23 00:00:00

Read original

cost_savings

I'm new to AWS and have been tasked to look at ways to optimize cost. I have gone through the best practices and strategies to do that: * Instance Right Sizing * Using Reserved Instances (RI) & Spot instances (SI) as appropriate (over On-Demand) * Auto Scaling Storage (Reduced Redundancy, Glacier) * Tagging strategies However, I have specific questions around the instance type. Apparently, we have a **r3.xlarge** (On-Demand) instance used for demos (for new clients) with 240 GB EBS (i.e. 4 CPU, 30.5 GB RAM), therefore it's not used very frequently.

2017-01-23 00:00:00

Read original

memory_usage, cost_savings

Similar Instances to

r3.xlarge

Consider these: