March 20, 2017 at 11:32 am #516290
I’ve just updated MyEclipse to Version: 2017 CI 3.
On the MyEclipse “Explorer view” I have configured: Folder Presentation –> Grouped, Package Presentation –> Hierarchical.
I have 3 large projects in the workbench. When I click any node on package tree, it take more than 30 secs to expand tree. However after expanding, the collapsing is instant and also opening same node again has no issues. Also the long delay is not present when opening a package tree that has only XML files, text files etc. The issue is only with java class packages.
Note:- Opening package tree in “Navigation View” has no issues.
The issue seems to be with JDK version I’m using. Configured in Windows–> Preferences.
When I use the default JDK coming with MyEclipse 2017, there is no slowness. As soon as I change to JDK 1.7.0_80 from Oracle(which I need to use), I get the slowness.
What is the reason for long delay. Is there an bug in the “Explorer View”. It is not possible to use MyEclipse 2017 with such a slow response time navigating to java class you want to work on.
Note:- I have used MyEclipse 2013, 2015 and 2016 with same projects/JDK and no issues on Explore View.
If you have tested MyEclipse 2017 with any other JDK 1.7.x version let me know and I can use it.March 20, 2017 at 1:49 pm #516296
I apologize for incorrect conclusion in previous post. The issue is NOT with different JDK version. I had ME 2016 workbench also open and must have tested on ME 2016 workbench after JDK change on ME 2017.
Anyway bottom line is MyEclipse Explore slowness is not because of JDK version used.March 20, 2017 at 10:28 pm #516376
I’m afraid MyEclipse 2017 is not compatible with JDK 7. You must run MyEclipse with the JDK that comes with MyEclipse, or another JDK that is at level 8 or above. This is a requirement for the underlying eclipse implementation, on which MyEclipse is based. You will likely have other problems if you continue to use JDK7 to run MyEclipse.
Note that you can still use other JDKs for your projects in MyEclipse, by defining other JREs (go to Window->Preferences-Java->Installed JREs to see your JREs and to add others). You can specify a default JRE for projects and use a different defined JRE for specific projects if you wish.
Please let us know if you have more questions.March 21, 2017 at 10:04 am #516425
I’m using JDK7 for my projects. I thought this might be the reason for slowness.
However MyEclipse itself is running on JDK8 as shown by myeclipse.ini config file I’m using below:12345678910111213141516171819202122-startupplugins/org.eclipse.equinox.launcher_1.3.200.v20160318-1642.jar--launcher.libraryplugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.400.v20160518-1444--launcher.defaultActionopenFile-vmbinary/com.sun.java.jdk8.win32.x86_64_1.8.0.v112/bin/javaw.exe-installC:\InstallSource\Genuitec\MyEclipse 2017 CI-vmargs-Xms512m-Xmx2048m-XX:+UseStringDeduplication-Dosgi.requiredJavaVersion=1.8-Dosgi.nls.warnings=ignore-javaagent:C:\InstallSource\Genuitec\MyEclipse 2017 CI\plugins\com.zeroturnaround.eclipse.optimizer.plugin_1.0.11/agent/eclipse-optimizer-agent.jar-server-XX:PermSize=256m-XX:MaxPermSize=256m-XX:+UseParallelGC-Xverify:noneMarch 21, 2017 at 10:40 am #516431
Apart from info in previous post about using JDK8 please note following:
1) ME 2017 IDE startup time is OK ==> No issues.
2) Navigating between different Perspectives ==> No issues
3) Creating projects/classes/Deploying apps ==> No issues
4) Navigation View –> Expanding class package tree ==> No issues
5) Explorer View –> Expanding class package tree ==> Unusually slow (25 secs to 45 secs)
So issue is specific to Explorer view. Note my projects are large with many java classes and sub packages. However no issues in ME 2016.
What would cause this slowness in ME 2017 ?March 22, 2017 at 3:19 pm #516640
Thank you for the detailed analysis so far – we would really like to get to the bottom of this slowness as well. In 2017, there are several new content providers that contribute to the MyEclipse Explorer view, which would account for possible performance differences wrt. 2016.
I have a few steps for you to try – these should help us figure out what is going wrong:
1) Can you try the Package Explorer view – does it exhibit the same delays?
2) If the Package Explorer view did not exhibit the delays, can you try the Project Explorer view?
3) In the MyEclipse Explorer view, from the view menu, choose the Customize View action item. In the resulting dialog, please switch to the Content tab. These are content providers that contribute to what is being displayed in the view – a buggy/inefficient provider could result in the slowness you experienced. My suggestion would be remove a number of them at a time and see if the slowness goes away. Once you find that there are no speed issues, you could re-enable the providers one at a time, to see which one causes the issues. Of course, you need to be trying with packages that will exhibit the speed problem (you mentioned that once a package is expanded, even if it took a large amount of time the first time, subsequent expansions would not be delayed)
4) As an alternative to #3, if you could get 3-4 thread dumps during the period during which the package is not expanded, that would help us figure out what process is running. To take a thread dump, you will need to run
jstack -l 9000 > dump1.txt
Please replace 9000 with the PID of the MyEclipse process, the jstack program can be found in the bin directory of any JDK installation. If you can generate 3-4 dumps (sent to different files, of course) during the period of slowness, and attach those files here, that could help a great deal.
Apologies once again for the inconvenience caused, I hope we’re able to get to the bottom of this.