Hi,
What's going on in the JVM after the mysql log looks good? I.e., what
happens if you take a thread dump?
Also, can you post your persistence.xml file (or at least the
properties section)? And are you running in an appserver or in a
standalone environment?
-Patrick
On Feb 1, 2010, at 1:20 PM, Tim daley wrote:
I'm loading a database with over 35,000 records into 100 tables. The
tables
may be linked up to 6 levels deep. (Root, A, B, C, X, Y, Z, Root_A,
Root_B,
Root_C, A_X, A_Y, B_X, B_Y, B_Z, A_C, B_C, C_Y, C_Z). There is a
single root
that contains all the other records (A, B, C). The records contain
other
structures (X, Y, Z) and some of the structures can contain other
structures.
The program builds all the data structure and then persists Root with
everything specifying cascade-persist in the orm.xml. That all runs
in a
couple of minutes. Then the commit is executed. A couple of minutes
later, I
check the mysql log and all the inserts have occurred along with the
commit
and quit.
It then takes over 7 hours for the OpenJPA commit to return, even
though all
records are actually committed and available. I'm running OpenJPA
1.2.0,
Java 1.6.0_10, MySQL 5.1.
Can anyone advise me on how to speed this thing up?
--
View this message in context:
http://n2.nabble.com/Extreme-performance-problems-with-OpenJPA-commit-tp4497009p4497009.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
--
Patrick Linskey
202 669 5907
