D
dbeavon
Guest
I use the client logging to correlate the logic (4GLTrace) with the elapsed time that is consumed in various parts of my code. I believe there are other tools like profilers that I should start using as well. The following problem may be better solved by a profiler (please let me know if that is the case, since I don't have much experience with ABL profiling). When I'm doing development work I may forget to compile a program, or I may deliberately leave programs uncompiled. However there is a runtime penalty associated with that (especially when -q is omitted). There can be surprising performance implications related to the on-the-fly compilation of ABL. The performance of doing runtime compile operations over client/server is not great, considering that schema has to be retrieved remotely. The problem I have is related to the client logging (using 4GLTrace). I can see where one program starts to call another, and I can see gaps of time (100's of milliseconds) where the program is paused, but it doesn't tell me whether that is because of the logic in my own code, or because of a runtime compile operation. It would be really nice if there was some way for the client logging to alert me about long-running compiler operations, due to the fact that r-code wasn't present. Is there a log entry type for that? Or are there any OE profiling tools that would quickly alert me to long-running compile operations?
Continue reading...
Continue reading...