Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
when I register a large number (10000+) of additional selectors in an Objective-C program using the runtime function sel_registerName, does this slow down my program? Not taking into account the time it takes to register those selectors.
Best regards,
Jochen
It will only slow down your application if you are creating an extremely pathologically named set of selectors that just so happen to all stack up in one bucket in the hash of selectors within Objective-C’s method cache.
Very unlikely. If you are seeing a performance issue, measure it with Instruments (or some other tool) and determine where it is before trying to optimize.
While rpetrich’s answer is correct, the amount of RAM per selector is minimal. In terms of the selector itself, it’ll just be an address’s worth of data. The actual selector value is not typically used. If the selectors are composed of statically allocated strings, it is unlikely that anything will actually touch the memory (unless your code does).
If you are dynamically generating the selector names, then the allocations will, obviously, take up memory.
(I am, of course, quite thoroughly curious why you are generating so many selectors. Quite the atypical pattern!)