This content has been marked as final.
Show 4 replies
-
1. Re: Performance Degradation
jeanluc Nov 23, 2009 6:59 PM (in response to dhook.donald.hook.gmail.com)The typical cause for such cases is a memory leak. You need to prove there isn't one before looking elsewhere (and transactional settings or pool size shouldn't matter in this case).
A second possibility is an incorrect implementation which keeps a single persistence context for all runs, which thus grows and grows.
-
2. Re: Performance Degradation
dhook.donald.hook.gmail.com Nov 24, 2009 1:11 AM (in response to dhook.donald.hook.gmail.com)I dont see any stacktraces in the log... so not sure the memory leak is it. I will have to look into your second suggestion. Thanks!
-
3. Re: Performance Degradation
asookazian Nov 24, 2009 11:29 PM (in response to dhook.donald.hook.gmail.com)Try profiling the app with JProbe, JConsole, or OptimizeIt, for example.
-
4. Re: Performance Degradation
dhook.donald.hook.gmail.com Nov 25, 2009 3:42 AM (in response to dhook.donald.hook.gmail.com)Thanks - I will give it a try.