Home/ Questions/Q 522969
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T08:24:32+00:00

Extraneous logging can be expensive. Therefore, I could turn off logging or heighten the

  • 0

Extraneous logging can be expensive. Therefore, I could turn off logging or heighten the logging threshold level to reduce logging during production mode (everybody knows that!)

However, what about the routines that are called to supply parameters to the logger statement?

Consider the logger statement.

logger.info(“number of windows=”+wins.size());

where wins.size() is an excruciatingly expensive operation – say, just for illustration of my (mis)understanding the problem.

If info logging is turned off, would wins.size() still be run.

Because when I do debugging, it seems that wins.size() gets stepped over first before log.info(). If so, what are your strategies to prevent expensive functions inside a logger statement from being executed if the logger is turned off?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    In C# 3.0 you could use lambdas to only execute a call to logging function when the logging is turned on. This is example using C# Common.Logging:

    Logger.Trace(m=>m("number of windows="+wins.size()));

    where Trace is defined like so:

    void Trace(Action<FormatMessageHandler> formatMessageCallback);

    and FormatMessageHandler is 

    public delegate string FormatMessageHandler(string format, params object[] args);

    So what happens is if tracing is turned on the m=>m("number of windows="+wins.size()) lambda gets called. If it’s off, the expensive call to get the window size is never made.

    • 0