Is it advantageous to call logging functions with format string + args list vs. formatting inline?
I’ve seen (and written) logging code that uses inline string formatting:
logging.warn("%s %s %s" % (arg1, arg2, arg3))
and yet I assume it’s better (performance-wise, and more idiomatic) to use:
logging.warn("%s %s %s", arg1, arg2, arg3)
because the second form avoids string formatting operations prior to invoking the logging function. If the current logging level would filter out the log message, no formatting is necessary, reducing computing time and memory allocations.
Am I on the right track here, or have I missed something?
IMHO, for messages that are very likely to be displayed, such as those given to
errororwarnit does not make much of a difference.For messages that are less likely displayed, I would definitely go for the second version, mainly for performance reasons. I often give large objects as a parameter to
info, which implement a costly__str__method. Clearly, sending this pre-formatted toinfowould be a performance waste.UPDATE
I just checked the source code of the
loggingmodule and, indeed, formatting is done after checking the log level. For example:One can observe that
msgandargsare untouched between callinglogand checking the log level.UPDATE 2
Spired by Levon, let me add some tests for objects that have a costly
__str__method:In practice, this could give a fairly high performance boost.