Summary: | Adding new class takes very long (>20s) (1GEUGFQ) | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Dani Megert <daniel_megert> |
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 2.0 | ||
Target Milestone: | 2.0 F3 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
Dani Megert
2001-10-10 22:52:42 EDT
PRODUCT VERSION: 0.118 Is this still occurring in our latest ? Might need to use a profiling tool Retested on build 20020212 First time: 23s Next time (another class with same layout): 13s Is this good enough? 23/13 seconds to add a simple class is too long in my opinion According to OptimizeIt, only 20% of the time is now spent recomputing the hierarchy. The rest is spent opening the types in the hierarchy to answer questions like isInterface(), or exists(), etc. We need to revisit the relationship between UI and Core on this. The best would be that the UI defines a set of functionality it needs to ask to the types so that Core can optimize these cases. Propose to defer post 2.0. Deferring Test TP#2 With the test case described above, it now takes 5s. 56% of the time is spent computing the hierarchy. The rest is in the UI. Closing Closed |