Debug logging is widely known, best for troubleshooting problems, in working within IMatch. The Help says, however, it is best, that under normal circumstances, the logging mode, be set to normal. Is performance significantly better (ie., faster), running the program, under Normal Logging?
Debug logging is intended to be used to track down specific problems. It produces a lot more data and also runs some additional tests which can reduce performance.
Keep the default logging unless you really need debug logging or I ask you to enable it temporarily to track down the source of a problem you have reported.
I find that debug logging has little effect on performance and keep it on. But this generates an irritating warning each time I open IMatch. Is there any way to stop this?
No. Debug logging should be off, unless needed. Hence the warning.
As I put in another post. Debugging Mode boots my IMATCH 5 times faster. I know, I am the exception. I will do as Mario says and keep it off unless it's needed to figure something out.
I' quite sure that this in unrelated to debug logging. Something similar has never been reported and there is no technical reason why logging more data and doing extra work would result in a better performance.
From my experience, this sounds like some of the strange effect a virus checker or other 'security' software would cause.
Just a thought: Maybe, the virus checker is interfering and intervening, in the presence of less work-load, with normal logging, because, it, nevertheless, see a different routine, and flags it.
Quote from: DigPeter on November 21, 2021, 01:49:36 PM
I find that debug logging has little effect on performance and keep it on. But this generates an irritating warning each time I open IMatch. Is there any way to stop this?
Same here. Always on debug logging since I had some issues that come up only occasionally and are not reproducible.
Can't see a perfomance issue.
Quote from: Mario on November 21, 2021, 01:58:50 PM
No. Debug logging should be off, unless needed. Hence the warning.
Ha, could catch.
You know your user well. ;D
I this warning would not be, I would use debug logging, but it is so akward, that I use normal logging.
So your idea works. :)