4

I am writing some real-time audio processing code, which is to be executed in an audio unit's render callback.

This thread is at the highest priority level the system recognises.

Apple instructs to minimise the amount of processing that goes on in this call. One of their recommendations is to avoid Objective-C method invocation.

But why?

What happens when an Objective-C method is invoked? what is the actual overhead?

P i
  • 29,020
  • 36
  • 159
  • 267
  • 2
    This has already been covered in other Stack Overflow questions. I believe the most detailed explanation available is on @bbum’s blog: http://www.friday.com/bbum/2009/12/18/objc_msgsend-part-1-the-road-map/ –  Apr 18 '11 at 08:05
  • @Bavarious: You should provide that as an answer as this blog post probably *is* the single best analysis of Objective-C method invocation. – DarkDust Apr 18 '11 at 08:08
  • That link scares the bejeezus out of me, 10 min ago I thought I was a professional software developer, now I feel like a total n00b, thx for that Bav :p – P i Apr 18 '11 at 08:43

1 Answers1

8

Objective-C method resolution is dynamic. In other languages such as C or C++, a function call is set at compile time, essentially as a jump to the address that contains the function. In Objective-C however, method calls are implemented as 'sending messages' which don't work in the same way. There is a lookup process involved instead of a hardcoded jump.

This lookup process as an overhead associated with locating the address of the method to run. It is very optimised, but for certain types of code the overhead can cause performance issues.

Mike Ash gives a great writeup on what happens with Objective-C messaging if you're interested in additional detail.

extremeboredom
  • 1,512
  • 12
  • 13