Community
Participate
Working Groups
[Usability] Test execution is slow with a large workspace. Since the Test execution dialog searches the entire workspace for TPTP test suites, it is slow (~10-15 seconds using just the TPTP test-results module) with a large workspace. Consider the solution used in https://bugs.eclipse.org/bugs/show_bug.cgi? id=98913.
There is a broad class of performance issues with large workspaces, most of which are centered around the fact that each testsuite must be loaded just to do simple operations, such as display the list of (filtered by type) testsuites in a dialog for launch config. Each test must be loaded just to find out what type it is so that it can be determined to display it in the dialog or not! Instead of trying to work around the problem, I would prefer an approach that looks at alternate ways of persisting the most commonly accessed data in testsuites (and potentially other test resources)such that it can be retrieved without loading the whole resource (or using markers, or other caching techniques).
In the Profiling and Logging related navigator views we use UI proxy objects (TRCAgentProxy which has 1-1 cross resource reference to the TRCAgent), that way we can postpone to load of the large resources (resources that contains TRCAgent) until the user really wants to view them. The TRCAgentProxy class has only the information (very small footprint) that is required to be shown in the navigator views.
I don't know if this continues to be a problem, but if so, I think it belongs to Jerome's area.
*** This bug has been marked as a duplicate of bug 160221 ***
Reporter: Please verify and close in preparation for shutting down the TPTP 4.4 release. Thanks.
Verified in TPTP-4.4.0-200706140100C.
