I took a first look with an eval copy of JProfiler while waiting for response from them.
All our startup is in the noise for a typical unit test. Do I need a really big service to see the problem that got us into this discussion:? On Wed, Mar 5, 2008 at 3:09 PM, Benson Margulies <[EMAIL PROTECTED]> wrote: > It's CPU that I'm proposing to hunt. > > > On Wed, Mar 5, 2008 at 2:52 PM, Bharath Ganesh <[EMAIL PROTECTED]> > wrote: > > > I had done some memory profiling on CXF 2.0.2, quite some time back. I > > think it was pretty stable except for some issues in PolicyEngine and > > HandlerChainInvoker which are fixed on the trunk. As of now I can see > > only > > this [1]. > > Please do let me know if you are suspecting a leak at some place. I > > shall > > look into it. > > > > Thanks > > Bharath > > > > [1]: > > http://www.nabble.com/Memory-leak-at-WSDLManagerImpl-td15131599.html > > > > On Wed, Mar 5, 2008 at 5:34 PM, Benson Margulies <[EMAIL PROTECTED]> > > wrote: > > > > > I might be willing to take a run at this. Can someone tighten up the > > idea > > > a > > > bit? If we were to cache service models, what would we key/invalidate > > the > > > cache against? How do we know that we subsequently need 'exactly the > > same > > > one'. > > > > > > For that matter, what about some profiling to make sure that there > > isn't > > > something we could tighten up? > > > > > > Anyone have a favorite tool for that purpose? > > > > > > >
