Thank you Jeremy for this important info. Many thanks also to yourself and others on this forum for the helpful and constructive comments.
I ran the benchmark again following Jeremy's instructions: Jeremy Bauer wrote: > > https://repository.apache.org/snapshots/org/apache/openjpa/apache-openjpa/2.1.0-SNAPSHOT/apache-openjpa-2.1.0-20101104.065025-93-binary.zip > > This snapshot has connection pooling included and enabled by default. If > you'd like, you can enable basic, un-tuned, statement batching and data > caching with these properties. > > property-3=<property name="openjpa.DataCache" value="true"/> > property-4=<property name="openjpa.jdbc.DBDictionary" > value="batchLimit=100"/> > I put the results on http://temp.jpab.org. The new results are presented as OpenJPA_R2. There are less failures now. All the tests pass when using H2 or HSQLDB in embedded mode. There are still some other issues. Again, any comments/criticisms are much appreciated. As an aside, I've noticed that testing an ORM is much more involved than testing an object database such as ObjectDB. There are many provider/database combinations, and each database has its own issues. Would you be interested in using JPAB (which is built for testing permutations) as a framework for running your own tests easily against various DBMSs? Regarding the database connection pool: Georgi Naplatanov wrote: > > Do not forget to enable statement pooling in database connection pool > configuration, if it is not enabled by default. > Thanks for the comment Georgi. I'm using the snapshot indicated by Jeremy which seems to have pooling on. If not, how can I enable this? How can I tell? Best regards, Ilan -- View this message in context: http://openjpa.208410.n2.nabble.com/JPAB-results-tp5693298p5715056.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
