IPhone / iPad: Does many NSLog () calls have an impact on application or memory performance?

Question

I would like to know if many NSLog () calls affect application performance or memory. Does anyone know of such a thing?

I want to put an NSLog () call in every function in my application (which is a lot) so that I can see the logs after and trace failures.

Thanks.

Answer 1

Yes. Therefore, I define this in my pch file.

#ifdef DEBUG # define DLog(fmt, ...) NSLog((@"%s [Line %d] " fmt), __PRETTY_FUNCTION__, __LINE__, ##__VA_ARGS__); #else # define DLog(...) #endif // ALog always displays output regardless of the DEBUG setting #define ALog(fmt, ...) NSLog((@"%s [Line %d] " fmt), __PRETTY_FUNCTION__, __LINE__, ##__VA_ARGS__); 

Instead of using NSLog, I use DLog and ALog.

(Note or copyright: I got this code long ago from some other SO message that I don't remember. Inserting it again from my snippet library)

Answer 2

Another simple solution to undefine NSLog

In the .pch file:

 #ifndef DEBUG #define NSLog(...) /* */ #endif 

Answer 3

Yes, it slows down performance, especially if a function should take a very short time, NSLog (which is an I / O process) will cause it to take longer than expected.