---
title: 'Rust vs. Go (Golang): Performance 2025'
source: 'https://youtube.com/watch?v=CsKNTwS9kic'
video_id: 'CsKNTwS9kic'
date: 2026-06-07
duration_sec: 210
---

# Rust vs. Go (Golang): Performance 2025

> Source: [Rust vs. Go (Golang): Performance 2025](https://youtube.com/watch?v=CsKNTwS9kic)

## Summary

This video compares Rust and Go performance using the Hyper HTTP server library on AWS EC2 instances, measuring throughput, latency, CPU, and memory usage.

### Key Points

- **Test Setup** [00:00] — Rust uses Hyper with Tokyo runtime; Go is tested on same infrastructure (M7A large EC2, systemd, EKS cluster).
- **Throughput Results** [02:10] — Rust achieved nearly 160,000 requests per second using only two CPUs, outperforming Go and all other tested applications.
- **Latency Results** [02:43] — Rust had better p90 latency than Go.
- **CPU Efficiency** [02:57] — Rust used less CPU than Go for the same workload.
- **Memory Usage** [03:10] — Memory was measured but deemed less important for this comparison.

### Conclusion

Rust with Hyper significantly outperforms Go in throughput, latency, and CPU efficiency, making it the fastest tested web server framework.

## Transcript

In this video, we'll compare Rust with Go, but this time using the most performant HTTP server library Hyper, which is based on the Tokyo asynchronous runtime. If you want to build
any web application, Tokyo runtime has become de facto standard and many frameworks such as Exum actually built on Hyper and Tokyo. Hyper is in fact the fastest framework I've tested
across all languages over the last year. I run all my tests on AWS and in this video I use exactly the same infrastructure as in the previous one. I use M7A large EC2 instances and run applications
using systemd service files while my clients and monitoring agents run on EKS cluster. All right, let's go ahead and run the test. It took around 2 hours and I compressed it to just a few minutes
while editing. So we measure latency using p90 percentile, throughput which is requests per second, as well as CPU usage and memory. This is the memory usage of the entire VM, so it might not
be as accurate as when I measured from the containers running in Kubernetes. As always, let me run this test for one more minute and we'll go over each graph one by one at the end of the test.
I sorry Thank you
Alright, first we have Threadput, which is measured as requests per second. Go reached
the same level as in the previous video, but Rust, once again, is the best and fastest application I've tested so far. It reached almost 160,000 requests per second using only two CPUs. None of
the other applications ever came close. Well, maybe Zeke was the closest one. Next, we have latency, which is one of the most important metrics. And again, Rust performed better than Go in this test.
Next, we have CPU usage, and you can see that Rust is more efficient using less CPU than Go application. And finally, memory usage, which is not really important for this video.
So let me know which language or runtime can compete with Rust, and if you can help to develop a simple web server in that language, it would be great. I have other benchmarks that you might find interesting such as Postgres vs MySQL, Redis vs Memcached and others.