[kepler-dev] [Bug 4764] New: slow performance after run

bugzilla-daemon at ecoinformatics.org bugzilla-daemon at ecoinformatics.org
Fri Feb 5 18:19:49 PST 2010


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

           Summary: slow performance after run
           Product: Kepler
           Version: 1.x dev
          Platform: Other
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: general
        AssignedTo: berkley at nceas.ucsb.edu
        ReportedBy: soong at nceas.ucsb.edu
         QAContact: kepler-dev at kepler-project.org


If I run any of the tpc workflows (e.g., tpc09), any subsequent changes to
Kepler (say changing workflow parameters) cause Java to peg one of my CPU
cores.  This includes canceling changes to RExpression.  I've seen this
behavior on Windows XP and 7.  While I haven't seen it under linux or OS X, I
haven't tested those as extensively.  I have tried small test workflows, and
haven't seen a particularly noticeable slowdown, so it may be related to the
size of the workflow run.  I have to restart Kepler to get things back up to
speed, and it's bad enough that I'm actually restarting Kepler after every run.

I'm not sure it's a memory thing.  java.exe is about maxed out on memory (~0.5
GB) in the Task Manager, but the Check System Settings window says I have 46%
free.  I was watching jstat, and changes don't seem to trigger a flurry of
garbage collection.

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


More information about the Kepler-dev mailing list