Upgrading Spark Studio's Editing PC
Spark Studio is a two-person video team producing school promotional films. Its current PC cost HK$7,500 three years ago and has a 4-core Intel Core i5, 8 GB of RAM, a 1 TB 5,400 rpm hard disk and integrated graphics. The team has just won a contract to edit 20 hours of 4K footage per month, exporting each finished video in 4K. In testing, the timeline stutters whenever more than two 4K clips are layered, the machine becomes nearly unresponsive when a browser and Photoshop are open, and a 12-minute video took 3 hours 40 minutes to export. Windows regularly shows low-memory warnings and the hard disk light stays on for minutes at a time. The upgrade budget is HK$9,000. A supplier offers a 32 GB RAM kit (HK$1,100), a 1 TB NVMe SSD (HK$700), an 8-core CPU that fits the existing motherboard (HK$3,200), a mid-range graphics card (HK$3,800), or a prebuilt machine with 16 GB RAM, a 6-core CPU, a 512 GB SSD and a weak GPU for HK$8,500.
1. Identify the two most likely bottlenecks from the symptoms, justify each with specific evidence, and explain why adding RAM alone will not make exports four times faster.
Read the worked answer
Two bottlenecks stand out.
RAM. The low-memory warnings and the freeze when a browser and Photoshop are open show that 8 GB cannot hold the working set. Windows then pages data out to disk. The disk light staying on for minutes is the signature of thrashing: the processor is waiting for page swaps rather than computing, which is why the whole machine feels stuck, not just the editing program.
Storage. A 5,400 rpm hard disk delivers roughly 100 MB/s sequential and far worse random access. Multi-layer 4K playback needs sustained hundreds of MB/s. The stutter appearing at three layers is consistent with the disk and RAM both being exhausted; the two interact, because insufficient RAM turns every clip access into a disk access.
Export time is different: encoding is mainly CPU-bound. A 4-core i5 is the limiting factor there, possibly helped by GPU acceleration depending on the codec. More RAM removes thrashing and makes the machine usable, but it does not multiply encoding throughput. That is why "just add RAM" fixes only one of three symptoms.
2. Recommend an upgrade plan within HK$9,000 and justify the order of purchases. Explain why the HK$8,500 prebuilt is not automatically the better buy.
Read the worked answer
One plan that fits: SSD HK$700 + 32 GB RAM HK$1,100 + 8-core CPU HK$3,200 + graphics card HK$3,800 = HK$8,800, leaving HK$200.
Order of priority:
- SSD first. It removes the page-file bottleneck and gives fast media cache and project storage. It is the cheapest change with the largest effect on responsiveness.
- RAM second. 32 GB gives headroom for 4K timelines, a browser and Photoshop together, and reduces writes to the page file.
- CPU third. This attacks the 3 hour 40 minute export directly. Check the motherboard socket, chipset and power supply rating before buying.
- GPU last. It helps GPU-accelerated effects and export codecs, but it will not rescue a machine that is thrashing.
The prebuilt has 16 GB RAM (half the planned figure), only 512 GB storage for 20 hours of 4K footage per month (4K material is large, so external storage would be needed), and a weak GPU. It also means reinstalling software and migrating projects. It is only preferable if the existing case, power supply or motherboard cannot take the 8-core chip.
3. Explain what virtual memory is and why the low-memory warning together with the constantly lit disk light indicates a problem that a larger page file will not cure.
Read the worked answer
Virtual memory is the mechanism that lets programs use more address space than physical RAM. Pages not currently needed are moved to a page file on disk; when they are needed again they are read back. This works because disk storage is cheap and plentiful, but it is far slower than RAM - a hard disk is thousands of times slower for random access.
When the active working set exceeds physical RAM, the system spends most of its time swapping pages in and out instead of executing instructions. That is thrashing: the disk light stays on, the interface stalls, and CPU utilisation may look low because the processor is waiting on I/O.
Enlarging the page file only gives the system more room to thrash. It does not reduce the number of swaps needed, and on a 5,400 rpm disk each swap is expensive. The real cures are to reduce demand (close applications, use proxy or lower-resolution media while editing) and to add RAM so the working set fits, plus an SSD so any remaining paging costs far less. A page file is a safety net, not a substitute for capacity.