<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Garbage-Collection on The Pragmatic Engeneer</title><link>https://blog.iaroslavtsev.uk/tags/garbage-collection/</link><description>Recent content in Garbage-Collection on The Pragmatic Engeneer</description><generator>Hugo -- 0.152.2</generator><language>en-us</language><copyright>2025 Aleksei Iaroslavtsev</copyright><lastBuildDate>Wed, 27 Aug 2025 21:58:31 +0200</lastBuildDate><atom:link href="https://blog.iaroslavtsev.uk/tags/garbage-collection/index.xml" rel="self" type="application/rss+xml"/><item><title>Taming Ruby's Memory Bloat: A Practical Guide to Processing Large Files</title><link>https://blog.iaroslavtsev.uk/posts/taming-rubys-memory-bloat-a-guide-to-processing-large-files/</link><pubDate>Wed, 27 Aug 2025 00:00:00 +0000</pubDate><guid>https://blog.iaroslavtsev.uk/posts/taming-rubys-memory-bloat-a-guide-to-processing-large-files/</guid><description>A case study on how we reduced the memory footprint of a data-processing Ruby script from over 200MB to under 70MB by ditching CSV.read and adopting a streaming, batch-processing approach.</description></item></channel></rss>