Tune Your Application

This section contains recommended application-specific tuning suggestions for performance improvement.

EJBs

• Stateless session beans and MDBs (message-driven beans) — For maximum concurrency, the pool sizes should be at least as large as the thread count of the execute queue that handles requests to such beans.
• Use concurrency strategy.
• Experiment with EJB pool settings.
• Use Call-by-reference.
• Cache EJBs.
• Increase the MDB pool size for asynchronous message consumption.

See Tuning WebLogic Server EJBs.

JSPs and Servlets

• Disable checks for JSP page checks and servlet reloading.
• Use in-memory session persistence, as described in Managing Session Persistence.
• Precompile JSPs, as described in “Precompiling JSPs” in Programming WebLogic JSP

See “Introduction to Programming” in Programming WebLogic HTTP Servlets.

JMS

• Avoid JMS message selectors and use multiple queues/topics to do message selection.
• Use asynchronous (onMessage) JMS consumers instead of synchronous receivers.
• Defer JMS acknowledgments and commits.

See the “WebLogic JMS Performance Guide” white paper on BEA dev2dev.

JDBC

• Tune your JDBC connection pool’s Initial Capacity and Max Capacity settings to complete database requests as fast as possible, rather than creating new connections.
• Cache prepared and callable statements used in your applications to minimize processing costs.
• Make your transactions single-batch by collecting a set of data operations and submitting an update transaction in one statement in the form.