Re: Dirty checking Performance issue

Thu, 03 Jul 2008 08:34:02 -0700 

Hi,
Can you describe your environment in a bit more detail? Is the OpenJPA code being called from a main() app? A Java EE app? 

-Patrick

On Jul 3, 2008, at 6:33 AM, Georg Raffer wrote:


Hi guys,


Are there any limitations concerning the persistence cache in  
OpenJPA? I'm having an application that loads several thousand  
entities and then adds some using em.persist(newEntity);



The problem is that persists takes extremly long (up to serveral  
seconds per entity on a server machine)!
The profiler shows me that the persist method stays very long in the  
dirty checking:



90,8% - 1.266 s - 31 inv.  
org.apache.openjpa.kernel.ManagedCache.dirtyCheck



Flushing or evicting entities from the session is not possible in  
this application.

Can anyone help with this issue?

bye, Georg
--
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger


--
Patrick Linskey
202 669 5907




Attachment:
smime.p7s

Description: S/MIME cryptographic signature






















					Reply via email to