TORPEDO Results for SolarMetric Kodo JDO 3.2

Single Server Configuration
Reported October 1, 2004
Results are unverified.

Description of the Submission

The TORPEDO JDO reference implementation source code was used unaltered. Kodo configuration settings were optimized for TORPEDO. In the JDO metadata, the JDOAuction.bids and JDOAuction.item fields were placed in the default fetch group. The JDOAuction.bids field was also configured to use a join for eager fetching (rather than a parallel select).

Contact Information

SolarMetric
gcamp@solarmetric.com
www.solarmetric.com/

Configuration

O-R Mapping System SolarMetric Kodo JDO 3.2
Submission Files package.jdo
ra.xml
TORPEDO Implementation TORPEDO reference implementation 8.25.04
Application Server BEA WebLogic Server 8.1 SP2
Database System Oracle 9.2, JDBC driver 9.0.1
Operating System
Configuration Notes For repeatablility, the application server was restarted prior to running each test. The database was restored prior to running the placeBid and place2Bids tests.

TORPEDO Operations

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.
listAuction 2 hits
listAuctionTwice
(as transaction)
2 hits
listAuctionTwice
(not transaction)
2 hits
listPartialAuction 2 hits
findAllAuctions 2 hits
findHighBids 2 hits
placeBid 4 hits
place2Bids 5 hits
TORPEDO: A Testbed of Object Relational Products for Enterprise Distributed Objects.
Copyright © 2005 Bruce Martin All rights reserved.