[kepler-dev] [Bug 5433] New: use 1024m instead of 512m for reporting suite

bugzilla-daemon at ecoinformatics.org bugzilla-daemon at ecoinformatics.org
Tue Jun 28 15:28:19 PDT 2011


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

           Summary: use 1024m instead of 512m for reporting suite
           Product: Kepler
           Version: 2.1.0
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: reporting
        AssignedTo: barseghian at nceas.ucsb.edu
        ReportedBy: barseghian at nceas.ucsb.edu
         QAContact: kepler-dev at kepler-project.org
   Estimated Hours: 0.0


Kepler has a max memory setting of 512m by default. Increasing this to 1024m
when using the reporting suite enables us to increase the hsqldb.cache_scale
setting to 18 (which greatly improves workflow execution time performance when
provenance is on by using more memory). Without making this change kepler will
lock up with heap space errors after a few executions of data intensive
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