Skip to content
TrackPodcasts
technologyMay 7, 201956:10pending

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

Ruby Rogues

Get every episode summarized

Each time Ruby Rogues publishes, we email you a written briefing from the transcript — the topics, who appeared, and any specific claims, with the ad reads skipped.

Email me new episodes

Free for 3 shows. No card needed.

About this episode

SponsorsPanel
  • 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.LinksPicksDave Kimura:Hongli Lai: Eric Berry:Charles Max Wood: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.

No transcript yet

This episode has not been transcribed. Request it and it moves to the front of the queue.

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

Ruby Rogues

0:00
56:10

More episodes

More from Ruby Rogues

View all episodes →