How One Engineer Fixed a Sidekiq Memory Bloat That Crunched Servers Every 72 Hours

Failed to add items

Sorry, we are unable to add the item because your shopping cart is already at capacity.

Add to basket failed.

Please try again later

Add to wishlist failed.

Please try again later

Remove from wishlist failed.

Please try again later

Adding to library failed

Please try again

Follow podcast failed

Unfollow podcast failed

How One Engineer Fixed a Sidekiq Memory Bloat That Crunched Servers Every 72 Hours

Listen for free

View show details

Episode 77 of The Software Engineering Podcast digs into a deceptively simple bug: a Sidekiq worker that ballooned in memory every 72 hours, forcing the ops team to restart it manually. Lucas and Luna walk through how one engineer discovered the culprit—a cached ActiveRecord relation that never cleared—and how a single call to `.reload` cut memory usage by 80 percent. They discuss lazy evaluation pitfalls in Ruby, the importance of profiling in production, and why a ten-line fix can save a team six figures in infrastructure costs. If you've ever fought a memory leak that only shows up after days of uptime, this episode is for you. #Sidekiq #RubyOnRails #MemoryLeak #BackgroundJobs #ActiveRecord #LazyEvaluation #RubyMemoryProfiling #DerailedBenchmarks #MemoryBloat #72HourBug #ProductionDebugging #EngineeringStory #SoftwareEngineering #Technology #FexingoBusiness #BusinessPodcast #CodeQuality #PerformanceOptimization Keep every episode free: buymeacoffee.com/fexingo

No reviews yet