<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Torrent on Experiment, Fail, Learn, Repeat</title>
    <link>https://www.hairizuan.com/categories/torrent/</link>
    <description>Recent content in Torrent on Experiment, Fail, Learn, Repeat</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>Copyright © 2026 Hairizuan Noorazman</copyright>
    <lastBuildDate>Tue, 08 Jul 2025 01:53:50 +0800</lastBuildDate><atom:link href="https://www.hairizuan.com/categories/torrent/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Solving the File Sync Bottleneck in tests: How Torrenting Could Be the Answer - Part 1</title>
      <link>https://www.hairizuan.com/solving-the-file-sync-bottleneck-in-tests-how-torrenting-could-be-the-answer-part-1/</link>
      <pubDate>Tue, 01 Jul 2025 00:00:00 +0000</pubDate>
      
      <guid>https://www.hairizuan.com/solving-the-file-sync-bottleneck-in-tests-how-torrenting-could-be-the-answer-part-1/</guid>
      <description>&lt;p&gt;At my job, one recurring technical challenge has been syncing massive files—often ranging from 10GB to 20GB—across multiple servers. We&amp;rsquo;re essentially copying over large iso files around to various servers. The current process still somewhat works but it is bandwidth-intensive, and increasingly difficult to manage as our the number of servers we need to sync this large file grows. Traditional solutions like rsync or SCP work, but they don&amp;rsquo;t scale well when the same file needs to be pushed to dozens of machines.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
