brunyuriy / quick-fix-scout

Automatically exported from code.google.com/p/quick-fix-scout
Other
1 stars 1 forks source link

Speculation Optimization: Eclipse proposal generation break-down #9

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Figure out what is the performance problem with generating proposals in Eclipse 
core.

Original issue reported on code.google.com by kivancmu...@gmail.com on 2 Dec 2011 at 4:38

GoogleCodeExporter commented 9 years ago
It turns out that the proposals are generating by first going through a big 
switch with respect to the compilation error's problem id (i.e., its type).

Now the question is: which kind of proposals take long to generate and why?

Original comment by kivancmu...@gmail.com on 2 Dec 2011 at 4:41

GoogleCodeExporter commented 9 years ago

Original comment by kivancmu...@gmail.com on 5 Dec 2011 at 1:19

GoogleCodeExporter commented 9 years ago
Removed owner.

Original comment by kivancmu...@gmail.com on 5 Dec 2011 at 4:22

GoogleCodeExporter commented 9 years ago
It turns out that if you try to retrieve proposals for a compilation error that 
is visible on the screen, the computation slows down a lot! 

As an optimization, the resolution of the original proposals are delayed until 
the quick fix activation. 

Original comment by kivancmu...@gmail.com on 11 Dec 2011 at 7:01

GoogleCodeExporter commented 9 years ago
Verified.

Original comment by kivancmu...@gmail.com on 13 Dec 2011 at 10:42