wood burning stoves 2.0*
The moose likes Performance and the fly likes Web application performance Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Java » Performance
Bookmark "Web application performance" Watch "Web application performance" New topic
Author

Web application performance

Shankar Narayana
Ranch Hand

Joined: Jan 08, 2003
Posts: 134
Hi all,

My application contains, Servlet, beans and jsp's , now for each request a requestType and beanType are passed as parameters and depending upon those parameters the servlet creates a new instance of the bean every time and i am making the bean object created to refer to NULL in the finally block. Does this sounds like a good approach?, any performance issues? what are the other procedures for a basic web application, I am not using any framework although its very much similar to Model 2 architecture.

Regards,
Shankar.


"Failure is not when you fall down; its only when you fail to get up again."
steve souza
Ranch Hand

Joined: Jun 26, 2002
Posts: 860
Assigning a null to a variable instance in a finally block should never be a performance issue. However, I am not sure why you are doing this as you say the object is recreated with each request and so a garbage collection candidate when it goes out of scope.


http://www.jamonapi.com/ - a fast, free open source performance tuning api.
JavaRanch Performance FAQ
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
 
subject: Web application performance
 
Similar Threads
Limitation on Spring bean definitions
How does a servlet know when it is being redirected to the right page
Servlet Context parameters
Hessian in Jboss
Servlets using beans' methods