DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Stateless JWT Auth Microservice Architecture With Spring Boot 3 and Redis Sentinel
  • Optimizing High-Volume REST APIs Using Redis Caching and Spring Boot (With Load Testing Code)
  • When Kubernetes Breaks Session Consistency: Using Cosmos DB and Redis Together
  • Rate Limiting Strategies With Redis: Fixed Window, Sliding Window, and Token Bucket

Trending

  • DZone's Article Submission Guidelines
  • How to Build a Local LLM Agent to Automate Work List Generation from Monthly Reports (With Jira Integration)
  • How to Submit a Post to DZone
  • A Spring Boot App With Half the Startup Time
  1. DZone
  2. Software Design and Architecture
  3. Microservices
  4. Reaching 500K Ops/Sec With Only 3 Redis Nodes

Reaching 500K Ops/Sec With Only 3 Redis Nodes

Modern load-intensive apps require a lot of work. You have to be sure that you're using your resources efficiently and getting the highest performance you can.

By 
Nikita Koksharov user avatar
Nikita Koksharov
·
Feb. 18, 17 · Opinion
Likes (5)
Comment
Save
Tweet
Share
15.0K Views

Join the DZone community and get the full member experience.

Join For Free

For a modern load-intensive application, it's important to ensure all available hardware resources are used with maximum efficiency. We have increasingly seen this type of applications employ in-memory a database like Redis for higher performance. However, that also begs the question, "Have we yielded the most performance out of Redis yet?"

In Redisson, while offering the most advanced features amongst all the Redis Java clients, we have put a lot of effort in optimizing its engine. We'll show you what it takes to reach 500K ops using Redis cluster with only 3 nodes. The benchmark environment was comprised of 3 AWS Elasticache Cluster nodes (m3.xlarge) and a single AWS EC2 instance (c4.4xlarge), which was where the benchmark application deployed. Only one Redisson PRO instance was used for the test. Here are the results:

Image title

Image title

Image title

Image title

Image title

Image title

We used the Redisson Benchmark module to graph these results.

Redis (company)

Opinions expressed by DZone contributors are their own.

Related

  • Stateless JWT Auth Microservice Architecture With Spring Boot 3 and Redis Sentinel
  • Optimizing High-Volume REST APIs Using Redis Caching and Spring Boot (With Load Testing Code)
  • When Kubernetes Breaks Session Consistency: Using Cosmos DB and Redis Together
  • Rate Limiting Strategies With Redis: Fixed Window, Sliding Window, and Token Bucket

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook