[kepler-dev] [Bug 4362] New: - component search performance

[bugzilla-daemon at ecoinformatics.org]

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

           Summary: component search performance
           Product: Kepler
           Version: 1.x dev
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: interface
        AssignedTo: aschultz at nceas.ucsb.edu
        ReportedBy: barseghian at nceas.ucsb.edu
         QAContact: kepler-dev at kepler-project.org


For awhile now I've noticed the first search of the library has become much
slower than it used to be, subsequent searches seemed to be fine, at least in
the same window.

Just recently I've noticed the more Kepler windows I have open, the slower
component search becomes. If I have 2 windows open when using WRP suite w/ my
eclipse build on mac w/ 4gb ram, doing a search for "string" in the second
window will generally crash Kepler with errors about Java heap space:
Exception in thread "AWT-EventQueue-0" java.lang.OutOfMemoryError: Java heap
space
        at java.util.LinkedList.addBefore(LinkedList.java:634)
        at java.util.LinkedList.add(LinkedList.java:196)
        at ptolemy.kernel.CompositeEntity.entityList(CompositeEntity.java:788)
        at ptolemy.moml.EntityLibrary.entityList(EntityLibrary.java:357)

I've also seen this occasionally, though I'm not sure if it's related:
2009-09-01 13:04:36.530 java[50021:80f] Apple AWT Startup Exception : ***
Collection <NSCFArray: 0x19e18d10> was mutated while being enumerated.
2009-09-01 13:04:36.531 java[50021:80f] Apple AWT Restarting Native Event
Thread

On my linux cmd line build, just using kepler suite, I also notice performace
issues, though it takes more windows for them to become severe. Once I have 7
kepler windows open, search for "string" takes about 12 seconds.