#Debug Display On' increases running time as much as 50% longer when on

[Gösta H. Lovgren-2]

Been playing around with DNA matching which involves 100's of millions of comparisons (see other thread) and got into subscript trouble so I turned #Debug Display On (see http://www.powerbasic.com/support/pb...ghlight=labels for enhanced use of Debug Display) which increased time to run as much as 50% when on.

Results:

with #Debug Display Off : 332,708,352 7.47 Seconds
with #Debug Display On : 332,708,352 12.00 Seconds

ONLY difference between (lotsa) runs is (un)remming Debug Display. Am not whining, moaning or decrying. Only sharing my experience. {sigh}

===================================================
“In the transition to statism,
every infringement of human rights
has begun with the suppression
of a given right’s least attractive practitioners.
In this case [involving pornography],
the disgusting nature of the offenders
makes it a good test
of one’s loyalty to a principle.”
Ayn Rand.
===================================================

[Michael Mattias]

>which increased time to run as much as 50% when on.

Looking at the help file for #DEBUG DISPLAY ON, it was pretty obvious this should be the case, since it pretty much implies the insertion of code to both check the ERR variable and to capture the "position word" after each statement.

But I agree with you, something a bit more explicit re runtime overhead in the help file would be superior to the current #MOMMY ON suggestion, "This mode should only be used during program development and debugging. It should never be used in a production program."

MCM