d8888 888 888      88888888888 888      d8b                                 888       888          888       .d8888b.           888                               
      d88888 888 888          888     888      Y8P                                 888   o   888          888      d88P  Y88b          888                               
     d88P888 888 888          888     888                                          888  d8b  888          888      Y88b.               888                               
    d88P 888 888 888          888     88888b.  888 88888b.   .d88b.  .d8888b       888 d888b 888  .d88b.  88888b.   "Y888b.   88888b.  88888b.   .d88b.  888d888 .d88b.  
   d88P  888 888 888          888     888 "88b 888 888 "88b d88P"88b 88K           888d88888b888 d8P  Y8b 888 "88b     "Y88b. 888 "88b 888 "88b d8P  Y8b 888P"  d8P  Y8b 
  d88P   888 888 888          888     888  888 888 888  888 888  888 "Y8888b.      88888P Y88888 88888888 888  888       "888 888  888 888  888 88888888 888    88888888 
 d8888888888 888 888          888     888  888 888 888  888 Y88b 888      X88      8888P   Y8888 Y8b.     888 d88P Y88b  d88P 888 d88P 888  888 Y8b.     888    Y8b.     
d88P     888 888 888          888     888  888 888 888  888  "Y88888  88888P'      888P     Y888  "Y8888  88888P"   "Y8888P"  88888P"  888  888  "Y8888  888     "Y8888  
                                                                 888                                                          888                                        
                                                            Y8b d88P                                                          888                                        
                                                             "Y88P"                                                           888   

All Things WebSphere

Concerns and issues relating to all versions of WebSphere Application Server

Monday, March 8, 2010

 

Pimp my websphere ... Reduce WebSphere Application Server startup time

If you do a lot of JEE application development on WebSphere Application Server (WAS) and cannot afford Rational Application Developer, you will often find yourself restarting WAS and wondering why you have to deal with restarting the server all the time. Why not save some time and develop on Tomcat or some other app server. As a developer in WAS, I face the same issues.

To help with this situation here is a cheat sheet to reduce your application server stop and start time. PLEASE NOTE THIS ADVICE IS ONLY MEANT WHEN DEVELOPING IN A SANDBOX environment. Some of these tips are illegal in 24 states... <just kiddin!>

1. Turn ON parallel start of the server. (default is true). Start the server on multiple threads. To view this administrative console page, click Servers > Application servers > server_name.

2. Server Component Provisioning: Start components when needed. Components started as they are needed by an application that is running on this server.

3. Run in development mode. Specifies that you want to use the JVM properties -Xverify and -Xquickstart on startup. Before selecting this option, add the -Xverify and -Xquickstart properties as generic arguments to the JVM configuration.

4. Set the JVM -Xms option equal to -Xmx to a value that is equal to your working set of your heap. Usually 1024MB is enough for development. Look at JVM tuning.

5. Uninstall all applications you don't need. Including system applications like the WebSphere admin console.

If uninstall is not an option then disable automatic start of applications.

wsadmin.sh –f deployConsole.py remove

6. Disable admin and application security.

7. Turn OFF the PMI service. PMI data collection is used to diagnose problems and tune application performance.

8. Turn OFF ODC Service. See APAR  PM07711: Allow the initialization of the On Demand Configuration component to be bypassed

9. Turn off the Dynacache Service in WAS v8 if you are NOT using caching. This is only possible in WAS v8.

10. Disable the WebSphere Application Server service log/activity log. This service is not essential to WAS and very few system administrator make use of the activity / service log. See on how to disable this service. This is the default in WAS v8.


11. Disable HAManager.  If none of the HA manager related services are being leveraged by your 
application or environment, the service can be disabled to eliminate the associated overhead. 

Labels: server performance

posted by Rohit Kelapure  # 6:36 AM

Comments:

Post a Comment

Note: Only a member of this blog may post a comment.

Subscribe to Post Comments [Atom]

<< Home

Archives

December 2006   September 2008   January 2009   February 2009   March 2009   September 2009   October 2009   November 2009   December 2009   January 2010   February 2010   March 2010   April 2010   October 2010   January 2011   February 2011   April 2011   May 2011   June 2011   July 2011   August 2011   September 2011   October 2011   November 2011   December 2011   January 2012   February 2012   March 2012   April 2012   May 2012   June 2012   July 2012   August 2012   September 2012   October 2012   November 2012   January 2013   May 2013   June 2013   July 2013   September 2013   October 2013   June 2014   August 2014  

Subscribe to Posts [Atom]