• Post Reply Bookmark Topic Watch Topic
  • New Topic

speeding of J2ee web application..

 
Jack Daniel
Ranch Hand
Posts: 163
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi e'body,
well, i have started working on an already created web-application using IBM websphere 3.5.3
and I was told to make some modifications and also speedify the application.IT is working pretty slow.
I have finished the modification part, but still to make it fast.
This application is working on the MVC structure ( servlets,java-beans and JSP ). This application was developed taking the help of WebSphere studio 3.5 & VisualAge for Java 3.5
It would be great if anybody can help me with the general ideas on how to make your
(JSP/servlets/java-beans) web applications run faster.
I am working with JDBC connection pooling.
One thing i have realized is that almost all the java-bean instances have been put in the session,
to extract data from the JSP(s); maybe this is a bad idea , having a lot of data in the session..??
I request you to help me out on how to make these kind of applications run faster.
I really appreciate your help.Thanks a lot
prashant
 
John Smith
Ranch Hand
Posts: 2937
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

It would be great if anybody can help me with the general ideas on how to make your
(JSP/servlets/java-beans) web applications run faster.

You can guess where the bottleneck is and optimize it, but there is a high possibility that the real bottleneck is some place else. What you need is to use a profiling tool (such as Borland OptimizeIt) to see the big picture.
Eugene.
 
Peter den Haan
author
Ranch Hand
Posts: 3252
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Seconded. Always follow the third rule of optimization: Profile Before Optimizing. (The first and second ones, by the way, are Don't and Don't... yet).
The amount of session data is only a problem if your application is running in a distributed container. In a distributed application, WebSphere persists all sessions in a database which gets painful above 2-4KB session data size.
Database access is another common bottleneck. Caching techniques are the usual solution.
Despite this, don't even think of optimizing stuff unless you know (as in: have measured) what the problem is.
- Peter
 
Jack Daniel
Ranch Hand
Posts: 163
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks a lot for your replies..
I appreciate..
i'll look into caching techniques..
and also into optimizeIt..
cheers
prashant
 
steve souza
Ranch Hand
Posts: 862
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
check out the following link for a list of profiling/performance resources:
http://www.javaperformancetuning.com/resources.shtml
Also check out
http://www.jamonapi.com
Steve
 
Kyle Brown
author
Ranch Hand
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Peter's right. Profile first, optimize later. BTW, some "likely suspects" to be on the lookout for in WebSphere code can be found here.
Kyle
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!