Slow Web Dynpro Applications

[Former Member]

Hi all,

Could anyone give some guidelines in order to reduce or minimize the request time for web dynpro applications. So far I could check the following pattern:

When I request a WD app conected to the ABAP stack of the same server using JCO the first time could take more than 30 seconds, the second time could be around 15 seconds and the third time could be less than five seconds. On each time I closed the browser and start over. If I restart my computer I got the same pattern. But If I clear all my cache and even delete the temporally files from my computer the first request to my WD app would be less than 5 seconds.

Could some one explain me how the Web Dynpro Runtime Environment and the browser cache works. Is there any configuration in order to recuce the cache files or maybe a workaround in ordet to reduce the request time without clearing the browser cache an temporally files.

Any suggestion, documentation or OSS notes would be appreciated.

Regards,

Orlando Covault

[Former Member]

Hi Ocovault,

While considering the few major flaws which developers generally do like overloading the hook methods like wdDoModify() and wdDoInit() should be avoided. keeping the methods simple and loosely coupled is also a good idea to optimise the performance you can recheck the methods for complex looping and keep it as simple as possible. Avoid repeated modification of view layouts when not necessary. Optimise Controller Life spans by changing it to when visible are the few tips which can make a huge difference for webDynpro application's performance. For detailed explanation please have a look to this Document which is really very effective and i specially recommend it for such cases. [Best-Practices for Optimizing Web Dynpro Java Application Performance|http%3A%2%2Fwww.sdn.sap.com%2Firj%2Fscn%2Fgo%2Fportal%2Fprtroot%2Fdocs%2Fmedia%2Fuuid%2Fd0857b3b-0775-2b10-60ac-ea031d35b6d9&ei=dwqjTff8K4POrQfwm5SFBw&usg=AFQjCNFusyav3e7PY6bDwwSjTL1qQDPZxA]

Regards

Jeetendra

[Former Member]

Hi all,

I already follow those best practices. I develop several WD app in the last few years. Hoever on the last implementation I got this extrange behavior and makes me wonder how can I fixed, and the first patern that I got was the browser cache and how the application is rendered each time faster without closing the browser, but when I restar the computer or even open a new browser I got the same slow behaviour.

Maybe you can recommend http trace tools o any other tool taht helps me to make a deeper analisys.

Regards,

Orlando Covault

[Former Member]

Hi Orlando Covault,

Yes you are correct if there are models used in wd applications it takes time to load first time we also faced similar issue and raised an OSS specially for this sap suggested few patches and the performance improved a bit. You should take up the same way i think.

Apart form that if you believe if the application is optimised properly. I'll check and may be i can suggest the similar patches which we used. I'd like to know which version you are working on.

Regards

Jeetendra

[Former Member]

Hi Choudhary,

We are on Netweaver 7.0 SP 16. I am also 99% sure that is an platform issue but so far I do not have any tool or mechanins to proove it. Maybe If I could get any recomendation on a platform level.

Also we are working with DC in NWDI so the jarm level is not an option.

Any suggestion would be appreciated.

Regards,

Orlando Covault

[Former Member]

Hi Orlando Covault,

We used [http watch|http://www.httpwatch.com] for monitoring those issue and sent the traces to them may be you can also try it if it helps. We used 7.2 sp 03 to resolve that and same patches for NWDI also. They mentioned that in 7.3 most of the issues will be resolved. Hope it will help.

Regards

Jeetendra

[Former Member]

Hi Jeetendra,

I test the http watch trial application I what I could see is that this toll gives me the request time elapsed and which Items are loaded from Cache and which don't.

However this information does not tell me much about what could be the problem, or maybe I could not find a usefull information.

Have tou ever resolve a performance problem using this tool?

Regards,

Orlando Covault

[Former Member]

Hi Orlando Covault,

No we didn't resolve the performance problem using this tool and we only analyze the problems due to which the performance was slow, anyways we use to sent these trace to them. I don't know what they found in that trace.

Regards

Jeetendra

[Former Member]

Hi,

I'd suggest you do some good tracing using a small application. It seems your issue lies in JCO, not in WDP rendering itself (which also proves to be very very slow). - At least you can really tell where your issue lies and act direct on it.

Try fine tunning the connection pools and caching mechanisms offered by NWAS.

I think you can find some good material on SDN, not sure if this would sort the issue for you.

D.

[Former Member]

Hi Daniel,

I also got the bad performance in applications that does not make any use of RFC ´s.

I think that is a general performance issue of the WD Framework because on the same Landscape relies several J2EE developments and they does not present the bad performance

Please any suggestion woold be appreciated.

Regards,

Orlando Covault

[Former Member]

Hi all,

Is it possible to be a platform problem with the JSESSIONID cookies, or maybe a general issue with the cookies that the SAP Dispatcher is using.

So far, on my own test with the http trace I got a pattern that every time that the application has bad performance there are url parameters pass to the WD Application like sap-wd-cltwndid, sap-wd-appwndid, sap-wd-norefresh, jsessionid between others.

Any suggestions?

Regards,

Orlando Covault

[Former Member]

Measure it, then draw your conclusions.

[Former Member]

Another suggestion will be to minimize the use of Group and Tray UI (especially nested). Transparent containers can be used instead. This will reduce the view rendering time a lot.

Also try to minimize coding in the wdDoModify() method.

Regards,

Sayan Ghosh

Edited by: sayan ghosh on Apr 11, 2011 10:02 AM

[Former Member]

You should first analyze where exactly the time is spent. Maybe the Web Dynpro console tool can help you with that:

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/03/10b540e4c5782ae10000000a155106/content.htm