Sponsors

Sentry use the code “devchat” for 2 months free on Sentry small plan
Triplebyte offers a $1000 signing bonus
RedisGreen
Cachefly

Panel

Charles Max Wood
Dave Kimura
Eric Berry

Joined by Special Guest: Hongli LaiSummaryEric Berry starts by sharing how Phusion and Phusion passenger changed his career and thanks Hongli Lai for his work. Hongli talks about where Phusion is now and shares what's new with passenger 6. The panel compares passenger and puma and Hongli explains why passenger is the better choice. The panel wonders about deployment strategies and Hongli shares what he has seen done with Passenger.Hongli discusses the article he wrote about memory bloat. He starts by explaining why he wrote the article. The panel discusses what causes memory bloat and how to identify memory bloat versus memory leaks. Hongli explains how the system memory allocator works and why people are using Jemalloc instead. The panel discusses Jemalloc and wonders why Ruby doesn’t adopt Jemalloc. Hongli shares his magic solution for solving the memory bloat problem and other tips for managing memory.Links

PicksDave Kimura:

Hongli Lai:

Eric Berry:

Charles Max Wood:

Open source sustainability podcast
https://podwrench.com/
Podcast assembly line
Podcast Laboratory
https://mybuild.techcommunity.microsoft.com/home#top-anchor
Oz con
https://elixirconf.com/2019
https://finconexpo.com/
https://podcastmovement.com/
https://go.2000books.com/

Special Guest: Hongli Lai .

Advertising Inquiries: https://redcircle.com/brands

Privacy & Opt-Out: https://redcircle.com/privacy

Become a supporter of this podcast: https://www.spreaker.com/podcast/ruby-rogues--6102073/support.

‌

Episode description

RR 411: What causes Ruby memory bloat? with Hongli Lai

Episode description