![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 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](https://miro.medium.com/max/1400/1*kB7rCM0XpoKHG2AIaddy0A.png)
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
![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 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](https://miro.medium.com/max/1400/0*EmmhijVk2W4Y2VaM.png)
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 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](https://pbs.twimg.com/media/Dr-p_y-U4AErGfj.jpg)
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
![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 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](https://miro.medium.com/max/1200/1*-k5nqnm1RR0KelAZ5xHXfQ.png)