As the word 'DEBUG' suggests itself, it provides very detailed log of activities while executing source code. Developers seek this information at very micro level in order to carry out root cause analysis if something un-expected outcome is thrown by the source code. Since, this is very detailed log it takes too much of system resources thereby depleting the performace. seeking DEBUG level log without impacting performace is not possible. SAP always recommend to set DEBUG level log severity only when it is required for analysis and restore the same to ERROR or FATAL after the traces have been collected.
As i said earlier also, since DEBUG provides very detailed level logging it is generally set as OFF. DEBUG is configured only when detailed tracing is required for troubleshooting and is switched off after the tracing has been collected. You are advised to keep DEBUG switched-off under normal server operations.
If you have received answers to your satisfaction,kindly mark the thread as 'Answered'.
It seems that you are talking about the DEBUG mode for ABAP programs and not DEBUG trace files. Kindly note that the performance could go down in a system where resources are less are too many ABAPers are debugging at the same time.
The difference between a program being directly executed and a program being debugged is that when a program is being debugged it takes much longer time as compared to direct execution because it keeps waiting for user intervention. During this time if you check you can see that the Work Process status is " On Hold". So if you are having less resources then you should limit the number of debuggers (abapers) or set the following parameter accordingly:
rdisp/max_debug_lazy_time
The lesser the time specified for this parameter, the lesser the " On Hold" time allowed for the program to wait for user intervention/dialog.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.