[kepler-dev] [Bug 5095] New: test kepler and wrp for memory leaks

bugzilla-daemon at ecoinformatics.org bugzilla-daemon at ecoinformatics.org
Wed Jul 14 15:56:35 PDT 2010


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

           Summary: test kepler and wrp for memory leaks
           Product: Kepler
           Version: 2.0.0
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: critical
          Priority: P1
         Component: general
        AssignedTo: barseghian at nceas.ucsb.edu
        ReportedBy: jones at nceas.ucsb.edu
         QAContact: kepler-dev at kepler-project.org
   Estimated Hours: 0.0


Oliver Soong reported having difficulties with memory leaks.  There are two
specific bugs about this, which I have set to block this testing bug.  In
addition, testing may reveal additional leaks, which should be fixed before 2.1
is released.  Here's Oliver's synopsis of the issues:

I think this is limited to the wrp suite, but Kepler’s performance degrades
significantly over time.  Provenance recording can become prohibitively slow,
and there is no native in-Kepler fix.  There is a large memory leak somewhere,
and many components are quite memory-intensive regardless.  Given the intention
to record executions and the large number of analyses scientists perform, I
suspect any dedicated user of Kepler will quickly encounter data management
problems.  In my case, I stopped using local repositories and began closing
Kepler after running any large workflows.

-- 
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