on 06-03-2008 12:04 PM
Hello Java Web-AS gurus,
we use for our portal a content management system, which generates JSPs. While using SPS13 of the EP 7.0 we noticed, that the compiling of the JSPs take very much time (around 5-8 seconds per JSP first time).
We search in the marketplace and find the note [1020365|https://service.sap.com/sap/support/notes/1020365], where is described, that SPS13 has performance problems by compiling JSPs. The issue should be fixed with SPS14. We update now our Quality system to SPS 15 and the JSPs only need 1-2 seconds to compile like before in older versions.
But now we patch also our productive system, but here the effect was less. Each JSP takes over 5 seconds to compile. While compiling, the javac process takes 100% of the CPU.
Our Quality is a central system installation on VM ware with 4GB RAM and MS SQL 2000 server on the same server. But our productive servers are in a distributed landscape, which 6 GB RAM on every Dialog Instance and a seperate MS SQL DB cluster. It has really much more power than the Quality system.
I can't understand, why even simple JSPs (3-6 lines) always take 5 seconds to compile. It seems, that the time is set somewhere.
Can somebody help us or have anybody a idea, what we can try?
Best Regards
Frank
Hi,
did you have a look at the properties of the servlet_jsp service?
Start the Visual Administrator and call the servlet_jsp service. After that click on the Properties TAB (should already be selected since it is the first TAB) => If this service is not available look for the Web Container Service
You could try to set the option CompileOnStartup to true (default is false). => This will enable the compilation of your jsps on startup of your engine!
This means that startup should take a little longer but you probably do not restart your engine very often so it should be alright.
With this option activated the rendering of your JSP should be faster than before.
You can also have a look at the other options
=> see http://help.sap.com/saphelp_nw70/helpdata/EN/ac/2bc55a78e54d60b561140048eaa80c/frameset.htm
Hope this helps
Cheers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Marcel,
unfortunately this is no option. We have about 30000 jsp on each of our six server instances and we restart our portal every week for backup reason. If we compile them all at startup, it will take a full week where the servers runs under full load!
I will need the reason, why the compiling takes so long.
Any further help with this problem?
Best regards
Frank
What JVM are you using? SAP JVM4? Are you using the same JVM version on all servers/server nodes? Check your JVM settings. Is there enough memory available on the servers, is there sufficient heap/permanent space for the JVM? Have you ruled out full garbage collection? See excellent blog on the topic.
Hi Sunil
Check out the portal performance best practice guide. It might give you some ideas / hints as to where to look.
http://www.docstoc.com/docs/40901129/Performance-Best-Practices-Guide-for-SAP-NetWeaver-Portal-70
As you can read in the guide, JSP slowness can be related to specific browser versions/issues.
Best regards
Tom
User | Count |
---|---|
83 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.