You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Berin Loritsch <be...@thetechnologiesgroup.com> on 2002/03/07 00:54:20 UTC
New AltProfile package
First of all, I want to congratulate you guys on a job well done.
The package has a simple, yet professional appearance and is easy
to use. However, I do have a few questions that you may be able
to help me out with (I have not jumped in the code yet):
1) Are you using the LogEnabled interface instead of the Loggable
interface?
2) Can you extend the example program to provide information about
the ProfilableComponentManager itself--with information about
lookups/second and releases/second?
3) Is it possible to have the GUI and the ProfilerManager in separate
VMs? It would be invaluable to determine the health of a servlet
like Cocoon, or blocks within Phoenix.
I liked the fact that the memory was well managed. When I tested it
with 100,000 doAction() events, I never exceeded 11M of max memory
in the JVM. That is a problem with JMeter's GUI event listeners.
Another thing that I thought might be useful when you are testing
systems with a profiler attached is to enable the ability to invoke
the garbage collector with the GUI. If the GUI is attached to an
external JVM, it should invoke the garbage collector in that VM.
Also, how exactly is the ProfilerManager listening for events?
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>