The TORPEDO Application was tuned so that it could take advantage of WebLogic specific features such as Batched Database operations and Relationship Caching. With this tuning enabled, the number of Database hits for the TORPEDO application was reduced to 20.

When we analyzed the TORPEDO application, we found that the submission made by The Middleware Company was on WebLogic Server 8.1 Service Pack 2, but it used the deployment descriptors (weblogic-ejb-jar.xml and weblogic-cmp-rdbms-jar.xml) from WebLogic Server 7.0 which has batching disabled by default. We changed the deployment descriptors to point to the 810 DTD, which enable batched database operations and ordered database operations by default. With batching turned on, multiple entries in the database table are updated in one batch of SQL statements. Also, the operations are ordered to take care of database constraints. This reduced the Database hits for the placeBid and place2Bids TORPEDO operations to 3 and 5 respectively.

The TORPEDO application was tuned further to use a WebLogic specific feature called Relationship Caching. This feature improves the performance of entity beans by loading related beans into the cache. Multiple queries to load related beans are prevented by the use of a join query. The TMC submission used relationship-caching feature for some operations on the AuctionBean only. On analyzing the application, we configured the relationship-caching in the deployment descriptor for some operations on the BidBean and UserBean and reduced the Database hits further.

Michael Chen and Mihir Kulkarni
BEA Systems Inc.
mychen@bea.com and mihirk@bea.com
Telephone: 415-402-7310 and 415-402-7722

The number of database hits required to accomplish the operation is given. Following the link provides raw results, SQL and additional operation specific configuration information and analysis.