TDK troubleshooting

This skill comes from a long session on 2026-09-25. It brought tdk-erp-system (107 services) up, measured it, and wasted a lot of the user's time along the way. Everything below marked measured or verified was run on the user's 16 GB MacBook Air (Docker VM: 8 CPUs, 7,934 MiB). Anything else is labelled as unknown.

How to work (the expensive lessons)

• Say what you measured, what you estimated, and what you don't know, in that order. Most of the frustration came from confident claims that a later measurement contradicted, such as "memory is ~16 MiB/container" (docker stats, which undercounts) and "112 s boot" (actually the launcher script). "I don't know yet, here is how I'd find out" is a good answer.
• Check machine load before blaming Docker, Tilt or the code. An overloaded Mac makes every tool look broken.
• Before anything that runs longer than about 5 minutes or starts dozens of containers, say so and give an estimate. A full ERP tdk up froze this machine once. Ask first.
• Give short status lines while waiting. Silence during long builds reads as "nothing works".
• Don't polish a proxy metric. Shrinking images didn't touch the real bottleneck. Ask what actually hurts (time, CPU, a freeze) and measure that.

First 60 seconds: triage