Why does tracking matter in Angular template control flow?

When a list behaves incorrectly, I test insertions, deletion, sorting, filtering, and replacement with freshly deserialized objects. An unstable or non-unique key can attach the wrong local state to a row, so this is a correctness issue as well as a performance issue. I choose keys that remain stable for the lifetime represented in the UI and avoid inventing indexes when the backend already owns identity. Profiling is useful for large lists, but a virtualized view may be the real solution when the DOM volume itself is excessive.