Hi Lahiru, [3] suggests some performance improvements on JPA. I am not sure whether all those suggestions are applicable to our scenario. It might be worth to try them and see the performance improvement, before completely giving up on JPA.
[3] http://java-persistence-performance.blogspot.com/2011/06/how-to-improve-jpa-performance-by-1825.html Thanks Amila On Fri, Sep 14, 2012 at 5:55 PM, Amila Jayasekara <[email protected]> wrote: > You can also find an another thread related to this in [2]. > > [2] > http://stackoverflow.com/questions/260618/orm-solutions-jpa-hibernate-vs-jdbc > > On Fri, Sep 14, 2012 at 5:41 PM, Lahiru Gunathilake <[email protected]> wrote: >> Hi Devs, >> >> I have been testing the new registry implementation and I have a feeling >> this is getting slow which is the issue that we are trying to address for >> jackrabbit implementation. This JPA implementation will add an extra >> complexity with a big performance overhead. >> >> I don't think we need to use a framework for this simple repository which >> has 11 tables with each having less than 6 columns in each table. My point >> is for a simple database like this, we really don't have to use a >> framework[1]. If our system it so damn complex we can live with the >> complexities and the performance bottleneck of JPA. >> >> WDYT ? >> >> [1]https://forums.oracle.com/forums/thread.jspa?messageID=10567940 >> >> -- >> System Analyst Programmer >> PTI Lab >> Indiana University
