[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: ABL Overhead Which is Due to R-Code Interpretation

  • Thread starter Thread starter tim
  • Start date Start date
Status
Not open for further replies.
T

tim

Guest
David, I'm not sure I understand exactly what you're looking for. When profiling is enabled, the AVM records a start time and an end time for every ABL statement. The AVM overhead time for a module (procedure, class, function, method, trigger block). The overhead is comprised of three things: 1) Time to instantiate the module; this may include time to read the r-code from the disk, initialize variables, check schema cache, allocate buffers, temp-tables, etc.; 2) Time to exit the module; clean up of the above allocated items. 3) Time to do any garbage collection which happens to have taken place while in the module. The overhead time is assigned to "Line 0" of the module. Garbage collection typically takes place in between execution of lines of code. In 12.1, we broke out the time spent doing garbage collection and assigned that time to "Line -2" of the module.

Continue reading...
 
Status
Not open for further replies.
Back
Top