Re: Cost of leaving debug statements in code

Mark Everhart wrote:
>
> Debate raging in current organization about the cost vs benefit of leaving
> debug output statements in production code. Currently, a private Boolean
> variable can be set On or Off by using public procedures. This variable is
> evaluated and if True then a debug package is called to output values of
> variables or whatever.
>
> The argument rages over the cost of evaluating the Boolean variable at
> numerous places in the code. Obviously, the poor souls manning the beepers
> would like to have the option of re-running a production job that goes down
> with the debug set on, so they can evaulate more accurately the cause of a
> problem, fix it, and go back to sleep or whatever.

The only way to resolve the debate is to run a load test, measuring system resources and response time, with the debug compiled in but turned off and with the debug not compiled in, and compare the results. Nobody can argue with that type of test. Personally, I would leave it in if at all possible.

-- 
---
Allen Kirby			AT&T ITS Production Services
akirby_at_att.com			Alpharetta, GA.