As a rule you can expect *any* orm framework to be slower than simple JDBC, there is simply more to do... What you gain from it is ease of maintenance and implementation which will save you time later (often a lot of time). As with anything, you need to weigh the benefits of any solution over another but in my experience most applications don't require such high throughput that anyone would notice a couple of milliseconds saved here and there... Of course it'll depend on what your doing :)
However... I've just been doing some work tonight, and am finding that begin() -> commit() transactions take longer and longer (in my case I have a very large update that is broken down into chunks). I haven't traced the problem yet and it may be configuration related, however the time grows exponentially. Does that sound like the same problem you are having? - Brill -----Original Message----- From: Patrick T [mailto:[EMAIL PROTECTED] Sent: Friday, March 28, 2008 3:55 PM To: users@openjpa.apache.org Subject: Slow JPA Hello Everyone, I'm just wondering if anyone else is finding JPA slower than simple jdbc implementations. I have tried setting up some of the attributes to Lazy fetch and I still find it to be extremely slow. This is causing my web pages to load in the upwards of 10 seconds. I have tried running the PCEnhancer and still takes a long time to fetch data. Does anyone have any suggestions to speed it up? Thanks. Patrick -- View this message in context: http://www.nabble.com/Slow-JPA-tp16360845p16360845.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
