To evaluate performance, we used a profiling tool available on the devkit. Our baseline sample project included unnecessary systems, such as audio, which we removed to streamline performance. By capturing profiling snapshots of both the unoptimised and optimised builds, we could quantitatively compare their CPU usage. While improvements were modest, they were measurable: a small reduction in system and user core utilisation, fewer active threads, and a decrease in ‘syscall’ activity. The optimised code ran on fewer cores and threads overall, demonstrating how even simple adjustments – such as stripping unused features – can lead to measurable efficiency gains. Although our analysis could have been deepened with additional snapshots, the exercise gave us experience in methodical optimisation and reinforced the need for profiling tools in professional development.
