Fpm Webdynpro

[Claribel Lizama]

Iam facing a performance issue with a complex webdynpro application we have made.When i checked the Trace via ST05 i could notice that it was the application load that was taking the maximum time, the SQL statements were consuming minimal time.But the HTTP trace does not give information about which exact components of the webdynpro application are causing the overhead, instead it shows the call time,execution time,send data size and idle time etc.

Is there some way to determine what component of the application is causing the maximum overload, for example a node, or overloaded component/view controllers etc? How can i reduce/optimise the time taken for application load?

3. Most of the times framework will effect the performance, because it will trigger the events as part of the framework. So try to check which part of code is executing number of times, try to restrict with conditions.(that will help you lot, but you need patience for debugging).

One way to check if the performance issues are due to the WDA framework itself or with application specific data, try running a standard Web Dynpro ABAP application, such as WDR_TEST_EVENTS or WDR_TEST_UI_ELEMENTS, from SICF transaction.

I get what you are saying. I know the component,view etc.What i don't know is what part of the component/view/controller etc are leading to the high processing time so that i can try to fix it. For example, a context node that has too many attributes which are not used anywhere.

I see what you mean. You mentioned the performance issue was on the application load, therefore I would start by analyzing the WDDOINIT methods of both the initial View and the Component Controller, I would also check if there is any Supply Functions for Context Nodes.

These are the methods that are called on application start. I will also check if there is any performance trace to see which Web Dynpro ABAP classes could be having a higher processing time and will update you if I find anything.

Thank You Mr Alladi,but i have already done all the optimization with respect to loops and queries and they are consuming only a negligible time. My question is that does the performance of the webdynpro application get affected by say if there are too many number of attributes in a context node or if there are too many nodes?

3a8082e126