|
|
When selecting trace event to log, this should give a better overview of consumsion of ressources in this area.
If you select database events (Before and After), a tab should form that agregate the time spend in database calls, per Natural statement, so you get a list of all the Natural statement in this application that caused a database call, and the number of calls and the elaps time spend in this calls.
| Created on Brainstorm | 12/10/2015 01:04 |
| Brainstorm ID | 3097 |
The NaturalONE Profiler Rich GUI Data Evaluation provides such evaluations. In the enclosed evaluation, I have selected the elapsed time as KPI (you may also select CPU time, database commands or Adabas command time). In the first pie chart, I use “Consumer” as criterion and select “Database”. In the second pie chart, it is displayed how the elapsed time is distributed over programs (its on the mainframe, every load makes database calls). I picked out one program which makes “real” database calls. In the third pie chart, we see how the database calls in this program are distributed on Natural statements (here: Read and Find for real calls). You can also view the distribution over the program lines, or Adabas commands or database files, or others.
The only drawback is that this works only for Profiler data collected in resources. It does not work for the online profiling.