[kepler-dev] [Bug 4642] memory usage & slowdowns

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=4642

Christopher Brooks <cxh at eecs.berkeley.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cxh at eecs.berkeley.edu
    Estimated Hours|0.0                         |80.0

--- Comment #2 from Christopher Brooks <cxh at eecs.berkeley.edu> 2010-07-16 08:49:52 PDT ---
See also bug 5095.

This bug should be primarily about performance, though memory management
will take part.

For information about performance, see
http://ptolemy.eecs.berkeley.edu/ptolemyII/ptIIlatest/ptII/doc/coding/performance.htm

The easiest way to track down performance issues is to create a small
non-gui Java program that runs the model and use a commercial tool like
JProfiler.  Oliver suggests jps -> jmap -> jhat.  

To close this bug a requirement should be that a wiki page is created about
how to track down performance and memory problems in Kepler.

Also, the performance test cases should be checked in.  Ideally, there
would be tests that would exercise these test cases and report an error
if the times changed more than a certain amount.  This is hard to do because
the times change depending on the machine and the load.

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.