All Things WebSphere
Concerns and issues relating to all versions of WebSphere Application ServerWednesday, October 10, 2012
How to improve RAD performance during publishing of application files
Ensure that your projects are single-rooted. Projects that are single-rooted can be directly consumed by WebSphere Application Server. If the project is not single-rooted, it needs to be copied as part of the publishing operation. If a project is not single-rooted, you see a warning message in the Marker's view.
Minimize the number of Java archives (JARs) in the WEB-INF/lib directories. If the JAR is no longer needed, remove it. If you see that the same jar is repeated in many lib directories, see if it can be moved to a shared directory on the server.
Start the test server in debug mode. This approach, which allows you to change the code by using the "hot method replace" and directly inserting the code into the running server, eliminates the need to perform a publish. There are cases where the Java virtual machine (JVM) cannot replace a method. In those cases, you get a warning message and then you need to publish the application.
Use Remote Method Invocation (RMI) as the connection type, because no polling is involved.
Remove unused applications. Removing unused applications shortens up your server start-up time.
Turn off your server's security, which improves the start-up time for your server as well as improving your publish times.
Periodically clean out the server's wstemp and temp directories.
Publish is an expensive operation because of all of the Rational Application Developer code, WebSphere Application Server code, and application code, for example, servlet destruction code, that must be processed. The best publish is no publish. It is best if you are in control of when publishes occur, so we recommend turning off automatic publishes. see figure
Look at this appendix of links for faster RAD performance with WebSphere
- Better hardware
- Shared EARs (binary modules)
- Annotations
- Publishing
- Shorter build time by tuning validation
- Only install what you need
- No circular dependencies
- Using a remote test server
- Tuning your anti-virus program
- Defragmenting disks
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]
Post a Comment
Note: Only a member of this blog may post a comment.