
- One Mac mini took 338 seconds to make a 3-second video and used 10.2GB of swap.
- Exchanging data over standard 1GbE Ethernet took 499 seconds per step.
- A direct Thunderbolt 5 connection cut the exchange to 8.13 seconds.
A single Mac mini took 338 seconds to generate a 3-second AI video. During the run, swap usage climbed from 6.4GB to 10.2GB. I decided to split the work across the 4 Mac minis at home.
Running a 50GB model on a 24GB Mac
The setup uses 4 M4 Pro Mac mini computers with 24GB of memory each. The video model is MiniMax H3, running on the open-source inference engine mmh3. Korea is an excluded region under the model's license, so separate approval was obtained to use it.
Each model file is about 50GB, too large to fit in 24GB of memory at once. On one Mac mini, generating a 3-second video at 672×384 resolution with 4 steps took 338 seconds. The Mac used swap throughout the run.

Splitting the work puts the network to work
mmh3 divides the tokens that make up a video across multiple computers. At every step, the Macs have to exchange a large amount of data.
I first connected them with standard wired Ethernet (1GbE). Sending 23.5GB, the amount exchanged in one step, took 499 seconds. That was longer than generating the whole video on one Mac, so splitting the work made no sense with that connection.
Thunderbolt 5 cuts the exchange to 8 seconds
I connected two Macs directly with a Thunderbolt 5 cable. The same 23.5GB transfer finished in 8.13 seconds. The result was consistent across 3 runs.
That is a difference of about 60 times. When running AI across multiple computers, the cable was the first thing to check.
| Connection | Transfer speed | 23.5GB exchange |
|---|---|---|
| Wired Ethernet 1GbE | 0.09GB/s | 499.57 seconds |
| Direct Thunderbolt 5 connection | 4.81~5.70GB/s | 8.13 seconds |

The Macs connect, but one does not respond
Changing the cable did not make the setup work right away. The two Macs appeared to be connected, but the one receiving the work never responded.
The cause was the macOS firewall. It was silently blocking incoming connections because the executable was unsigned. I kept the firewall on and fixed the problem by adding mmh3 to its allowed rules.
There was one more network setting to change. I turned off the default Thunderbolt Bridge in macOS. With several Macs connected in a loop, leaving it on had caused a network storm that froze a Mac. I assigned a separate static IP address to each link.
Next, it was time to try running the job on 2 Macs. The command finished without a problem, and a video appeared. But one Mac had done all the work by itself. There was not a single error message. The story continues in Part 2.
댓글
댓글 쓰기