memory - Puma not outperforming Unicorn (Rails 5.0 app) - is this normal? - Stack Overflow
Unicorn vs Puma: Rails server benchmarks
ruby on rails - Memory is not getting released after use In Puma Docker Container - Stack Overflow
Configuring Puma, Unicorn and Passenger for Maximum Efficiency
Migrating EpicPxls.com to Docker + Rails + Puma + Nginx + Pagespeed + PostgreSQL + Redis + Memcached on Heroku | by Ciocanel Razvan | EpicPxls
Configuring Puma, Unicorn and Passenger for Maximum Efficiency
Puma vs Phusion Passenger : r/rails
Why puma workers constantly hung, and how we fixed by discovering the bug of Ruby v2.5.8 and v2.6.6 | by Yohei Yoshimuta | ITNEXT
Nate Berkopec on Twitter: "Best memory usage of a Rails app that I've ever seen was someone running 30 Puma processes with 6GB. That's 200 MB per process. This was a very
🗜Reducing Rails Memory Usage by ~15% | by Christian Gregg | Medium
Puma vs Unicorn vs Passenger: Ruby App Servers Compared | Scout APM Blog
To Thread or Not to Thread: An In-Depth Look at Ruby's Execution Models (2023)
Memory usage keeps going up over time · Issue #342 · puma/puma · GitHub
Puma is the Preferred Web Server for Rails -- Planet Argon Blog
Puma: A Ruby/Rack Web Server Built for Parallelism
Deploying Rails Applications with the Puma Web Server | Heroku Dev Center