Bug 544054 - Open Type Hierarchy on IResource takes >2x longer depending on installed bundles
Summary: Open Type Hierarchy on IResource takes >2x longer depending on installed bundles
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.11   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: performance
Depends on:
Blocks:
 
Reported: 2019-02-01 18:19 EST by Andrey Loskutov CLA
Modified: 2023-01-26 15:06 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrey Loskutov CLA 2019-02-01 18:19:50 EST
4.11 head, running on JDK 11 (if it matters).
Just tried to open Type Hierarchy on IResource and it stays for a minute or so and uses lot of memory (jumps from 800 MB to 2 GB). 

Open Type Hierarchy on SortedSet (with way more children) takes a second, on Collection three seconds and uses ~300 MB. This can't be normal.

I will try to profile this tomorrow, now it is a bit too late.
Comment 1 Andrey Loskutov CLA 2019-02-02 11:46:15 EST
OK, just checked 4.9, 4.10 and 4.11 with new workspaces. Looks like we resolve IResource hierarchy instantly if I have not used "Add all plugins to Java search", and we need 12 seconds in 4.9/4.10 to resolve after that.

Still, with 4.11 I20190201-1800 it needs 34 seconds, and because it does whatever it needs on UI thread, this is not acceptable.

So we have a regression in 4.11 regarding the open type performance. I will report another bug for the blocking task.
Comment 2 Andrey Loskutov CLA 2019-02-03 05:44:41 EST
OK, after some more experiments I've found that this is not a difference in the platform version, but a difference in the installed bundles that triples the time. I will check which bundles are causing this.
Comment 3 Eclipse Genie CLA 2021-01-24 11:14:04 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 4 Eclipse Genie CLA 2023-01-26 15:06:40 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.