I Ran a Whole Content Pipeline on a $7 VPS With 2GB of RAM (And the 3am Crash That Taught Me Why)
Description and use
A content pipeline on a 2 GB VPS crashes at 3 am due to memory pressure. Fixes include single‑process execution, peak memory measurement, garbage collection, input chunking, idempotency, and swap monitoring.
Problem
A cron‑driven content pipeline crashed at 3 am on a 2 GB VPS, making the server unreachable with no logs.
Outcome
The pipeline stopped crashing and operated reliably on the 2 GB VPS.
Workflow
- Run one heavy job at a time
- Measure peak memory for each step
- Force garbage collection between heavy steps
- Chunk input into smaller batches
- Make jobs idempotent
- Monitor swap usage
Evidence
The cron job ran at 3am. By 3:02 the server was unreachable.
One process at a time. This alone ended the crashes.
Measure the peak, not the average.
- Record date: 2026-10-02T15:55:53.563Z