Partners can now generate a performance trace from SAP cloud application studio ,which will help you to analyze the execution time of a script and the time taken by the following individual constructs within a script.
“Prerequisite: The script files need to be reactivated after the 2005 upgrade before performance traces can be taken”.
- Mass Create
- Foreach Loops
- Standard/custom action calls
- Only Custom reuse library function
This functionality is the extension of the current tracer and you just need to do the normal tracing buy executing your custom actions or determinations from the front -end UI.Once the trace is completed you can click on get trace details and then you will see a new tab called “Performance Trace” which is added in this 2005 release.
To view the detailed analysis of script execution, follow below steps:
- Navigate to Debug Windows Trace Explorer.
2. Execute the normal business flow and end trace.
3. Navigate to the Trace Explorer tab and select a particular trace to see the details and In the Performance Trace tab, you can see the detailed analysis of script execution.
How to Perform ABSL performance trace for ODATA services:
You have to create CBO or XBO and enhance your ABSL logic in any of the scripts.
As shown below in the sample example we have enhanced Opportunity BO and created After- Modify and Before Save scripts. In After modify we are creating, querying and using foreach loop for an instance.
Open Trace Explorer and start Tracing as explained above. Below is the screen shot on how to start trace.
You can see that in below example trace has been activated for my development user.
Now Execute Post call through Postman for executing above ABSL logic and maintain same user (development SDK user) in Authorization for post call.
Once Post call is Executed, Go back to Cloud Application Studio and stop Tracing and View latest Trace
Double click on Trace for ABSL logic of your solution and Go to Performance Trace tab
Note: Traces would be shown for all ABSL of all activated solutions in particular tenant which gets executed.
In Performance Trace tab, Check Execution time for Full script and also for different Constructs used in Scripts.
How to perform ABSL performance trace for MDRO
Define ABSL logic in your Custom Action ABSL of Custom Business Object (CBO) and create MassDataRun.run on the same CBO.
- Start Tracing in trace explorer
- Execute MDR run from the UI (login to UI with same user as SDK user)
- Once Execution of custom action ABSL is done (In SDK Stop Tracing )
- Check Performance Trace for Custom Action ABSL as shown above steps.
Below are some screen shots explaining the same:
Login to the C4C/BYD front end application and execute the MDRO run and wait the application log is finished successfully.
Check the MDRO action is the trace explorer sequence and double click on Trace for ABSL logic of your solution and Go to Performance Trace tab as explained earlier.
- Performance trace is an actual run-time tracer which will calculate the total time taken for execution a script time in seconds.
- It also explains you in detail about the type of Construct, name of the construct, the line number of the corresponding absl script and the number of instances retrieved by the operation.
- If you see any Add on is causing performance issue in your system this functionality will help you to find out which Constructs are taking more time.
For example you are using a foreach loop, in your performance trace the foreach start will show the number of the instances retrieved by a query or action with the absl line number and foreach End will explain you total time taken to execute the loop.
For more details please refer to our SAP help documentation whats new section –Performance Trace of script using trace explorer
Hope the enhance version of tracking feature with “Performance trace” will be helpful for all of you.
This feature is not applicable for offline ABSL.