Poor Performance of the proj?

[Former Member]

Hi,

1. If we login to the portal page, it will tak more time to load the front page? I am using WD applications in the portal page.Front page consists of Drop downs by using simple type. Here no RFC's are used. wat will be the issue?

2. The same problem exists while giving search critria. It will tak more time to load data. Here RFCs are used.

Note: I am not using any pdfs in my application.

Why its taking more time.

And also tell is it problem with portal side or webdynpro side.

Pls help. Its very urgnt.

GS

Edited by: Sathishkumar GS on Sep 12, 2008 11:51 AM

Edited by: Sathishkumar GS on Sep 12, 2008 11:56 AM

Edited by: Sathishkumar GS on Sep 12, 2008 12:56 PM

[Former Member]

Hi Sathis,

Initially you have to find out the performance bottle necks in your Web Dynpro application. Few tools are available in Web Dynpro to find out these problems. The performance related issues can optimise in many ways ..like Web Dynpro coding side, cache settings , J2EE engine settings and etc......

Before start modifying the changes on code first identify the reasons for poor performance. This blog clearly explains how to identify the performance related issues in your application?

Some example here on how to measure the performance related issues in Web Dynpro applications.

http://help.sap.com/saphelp_nw04s/helpdata/en/b5/7e1141e109ef6fe10000000a1550b0/frameset.htm

http://help.sap.com/saphelp_nw04s/helpdata/en/4f/8dd7406efa702ae10000000a155106/frameset.htm

http://help.sap.com/saphelp_nw04s/helpdata/en/ad/32b5403fd63426e10000000a1550b0/frameset.

Thanks

Krishna

[Former Member]

Hi

This may be a problem on dynpro side.

Remove code from wdDoInit() for loading/calling of data if any.

Try to load data after displaying page via methods / on actions of UI Elements.

Refrain from calling data at Initialization of page because it will execute logic being deployed in Init() while loading page

If there is any table UI Element and u r filling it on initialization of page may be the cause.

Also check dynpro's performance without portal. If it is still taking that much time then surely problem on dynpro side because of bad design.

Try loading/accessing data in component controller and use view controller for displaying data only. you may call methods of component controller in view.

While accessing FM/BAPI if it take long then may be problem of Jco Connection which is being called by many models within same application. Try using seperate Jco's for different models in same appl.

Mandeep Virk