geronimo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <>
Subject Re: Geronimo 2.1.1 running a report 2-3 times slower than Geronimo 1.1.1
Date Fri, 05 Dec 2008 01:46:02 GMT
The only thing that comes to mind so far is that ejb cmp 2.1 entity  
beans have been completely rewritten to use jpa rather than tranql.   
There were some reports early on that in some situations this was a  
lot slower, but I think that in other situations it was faster.  Are  
you using cmp 2.1 entity beans?

david jencks

On Dec 4, 2008, at 5:04 PM, Andrew Thorburn wrote:

> This has recently cropped up at my workplace - We have a report that
> runs every night and dumps a reasonable chunk of the database to a
> text file. The report itself is quite inefficient (it stores
> everything in memory until it's written to the text file, for
> example), but a simple switch from Geronimo 2.1.1 to Geronimo 1.1.1
> results in the file taking 2 - 3 hours instead of 6 - 8 (or more!)
> hours. I'll be looking into this myself, trying to pinpoint if it's
> our fault or Geronimo's fault, but I was wondering if anyone had any
> ideas, or if there are any known areas where Geronimo 2.1.1 is slower
> than Geronimo 1.1.1? Likely places are in the XML libraries, or in the
> Database Pool/Connectivity from what I understand.
> Any suggestions on how to investigate this would also be appreciated.
> I'll add in profiling code to our application in the relevant places,
> but I'm not sure what else I should be doing to get to the bottom of
> this?
> Thanks,
> - Andrew Thorburn

View raw message