What causes hidden performance issues in Objective-C messaging systems?

Frequent dynamic dispatch, cache misses, and runtime introspection can degrade performance.

Objective-C messaging is fast when cached but expensive on first lookup. Heavy use of respondsToSelector, method forwarding, and dynamic method resolution increases CPU overhead. Additionally, repeated small message sends in tight loops amplify dispatch costs compared to static languages.