Eclipse Community Forums: Java Development Tools (JDT)

Home » Language IDEs » Java Development Tools (JDT) » Horrible Lag(Consistent lag at all times on every install of Eclipse. )

Horrible Lag [message #1798355]

Fri, 16 November 2018 01:01

Eclipse User

I've been using Eclipse for the past handful of years without any issues.
But since I've recently upgraded my PC, I've been having a constant issue that forced me to switch to a different IDE for awhile.
Whenever I open eclipse (New install, default everything), it immediately has consistent lag spikes every second or so, even when a project isn't open. The rest of my system will remain unaffected. Said lag will effect everything UI related, from typing to simply trying to select something. I've tried with the most recent version of Eclipse. Also tried with Oxygen, and Mars, making note to remove all folders Eclipse made during install (to my knowledge);
/user/.p2/*
/user/eclipse/*
As well as my workspaces.

Normally I'd be fine to just sticking to the other IDE I've been using the last couple months. However, I have a old project that heavily relied on Windowbuilder, and using Eclipse with Windowbuilder again would make working with said project 'much' easier, rather than sticking with working with the code directly. So I'm stuck trying to get Eclipse to work right.

I'm unsure what information should be given to help debug the issue. Is there a log somewhere or anything to that effect? I'll help in any way I possibly can to help resolve this.

Here's my PC specs;
CPU: FX-8350 4.0GHz
RAM: 8GB
GPU: Radeon HD 5700
Windows 7 Ultimate SP1 x64

Re: Horrible Lag [message #1798506 is a reply to message #1798355]

Mon, 19 November 2018 23:09

Eclipse User

Did you try increasing the allocated heap size? This can be done via the ini file - https://wiki.eclipse.org/Eclipse.ini

Re: Horrible Lag [message #1798515 is a reply to message #1798506]

Tue, 20 November 2018 00:41

Eclipse User

Yep. I tried to set it to use 3GB, didn't seem to effect the lag at all.

I'm currently just using a virtual machine with Eclipse installed on it, and *that* works fine, for some reason. A bit overkill, but it works, so meh.
The VM is using the same OS setup and eclipse setup as the host (my main PC). So I'm unsure why it works fine in the VM but not on my PC.

Re: Horrible Lag [message #1798604 is a reply to message #1798515]

Tue, 20 November 2018 18:31

Eclipse User

If the "lag" materializes into "freezes" of more than a second or so, you might find out more by taking a few stack traces, see also https://wiki.eclipse.org/How_to_report_a_deadlock

If it's about shorter periods, which you cannot easily capture, you may also switch on "UI Responsiveness Monitoring" in the preferences.

Re: Horrible Lag [message #1798956 is a reply to message #1798604]

Tue, 27 November 2018 18:58

Eclipse User

I've just started using a Virtual Machine with another install of 7 and I've been using Eclipse on that.
It's a horrible work around, but it seems to work for me I guess.

Re: Horrible Lag [message #1798957 is a reply to message #1798956]

Tue, 27 November 2018 19:13

Eclipse User

As mentioned, if you want anybody to help, stack dumps are what we need.

Re: Horrible Lag [message #1798965 is a reply to message #1798957]

Wed, 28 November 2018 01:13

Eclipse User

Yes, jvisualvm is part of the JDT and can be used to produce nice stack dump. E.g., like this one to figure out why my IDEs are taking several minutes to luanch:

   java.lang.Thread.State: RUNNABLE
	at java.io.WinNTFileSystem.getLastModifiedTime(Native Method)
	at java.io.File.lastModified(File.java:943)
	at java.util.zip.ZipFile.<init>(ZipFile.java:219)
	at java.util.zip.ZipFile.<init>(ZipFile.java:149)
	at java.util.zip.ZipFile.<init>(ZipFile.java:163)
	at org.eclipse.update.internal.configurator.SiteEntry.detectPackedPlugin(SiteEntry.java:345)
	at org.eclipse.update.internal.configurator.SiteEntry.detectPlugins(SiteEntry.java:322)
	at org.eclipse.update.internal.configurator.SiteEntry.loadFromDisk(SiteEntry.java:627)
	at org.eclipse.update.internal.configurator.PlatformConfiguration.reconcile(PlatformConfiguration.java:1003)
	at org.eclipse.update.internal.configurator.PlatformConfiguration.<init>(PlatformConfiguration.java:118)
	at org.eclipse.update.internal.configurator.PlatformConfiguration.startup(PlatformConfiguration.java:616)

From this I could determine that Eclipse is reading all 58,000 bundles in my bundle pool on startup whenever a bundle is added to the pool.

If you can't provide a test case that reliably demonstrated/reproduces your performance problem, the JDT team needs to know where the problem lies and it's only with such stack traces that they'll be able to do that.

Re: Horrible Lag [message #1799168 is a reply to message #1798965]

Fri, 30 November 2018 15:56

Eclipse User

jvisualvm is part of the JDK
:)

Re: Horrible Lag [message #1799188 is a reply to message #1799168]

Sat, 01 December 2018 03:11

Eclipse User

Hi

I observe sometimes incredibly poor Eclipse performance in ways that are clearly not observed by platform developers, but which are observed by the occasional forum critic. My suspicion is that there are multiple factors that escalate disproportionately as a variety of projects each contribute their distinctive indexing / building that run regardless of UI visibility. Even JDT now seems to have a new advance lookup to burn time. Stack dumps are not necessarily helpful since multi-cause/multi-file consumers can evade the accidental jvisualvm interception. The status text is often disconcerting. When the Progress View can be displayed, it hints at many untoward activities. Unfortunately many activities are secret; perhaps non-Job CPU burning should be prohibited. It appears that a dedicated instrumentation is necessary to log how long each job ran and on which thread, particularly what triggered each build job. Then after some mandatory coffee break, the jobs that ran during the coffee break can be reviewed.

Are there some standard debug options that will do this? I see many options but no useful documentation.

In the old days it used to be possible to just import an offending project as a plugin/fragment and modify it. Nowadays many plugins have a broken source plugin. Any suggestions on how it is now possible to add custom instrumentation to a platform plugin without struggling with the entire OOMPH of the platform?

The UI freeze detection initiative was a good idea, but we really need a corresponding CPU burn detector. https://bugs.eclipse.org/bugs/show_bug.cgi?id=415284 and its references hint at some of the real problems that may arise through platform extension. My patience with my poor Eclipse performance is finally wearing thin. I need to investigate. Maybe it is my own projects that cause my problems. Help-wanted.

Regards

Ed Willink

Re: Horrible Lag [message #1799215 is a reply to message #1799188]

Sun, 02 December 2018 10:46

Eclipse User

Hi Ed,

Quote:

Stack dumps are not necessarily helpful since multi-cause/multi-file consumers can evade the accidental jvisualvm interception.

You're absolutely right, that stack dumps are no silver bullet, but in many cases it's the only straw that we can clutch onto.
If stack dumps don't help, the next canonical tool for investigation is a profiler. Are you in the position to use such a tool? (Most people seem to be using YourKit, but there may be many other suitable tools in this group).

Quote:

In the old days it used to be possible to just import an offending project as a plugin/fragment and modify it. Nowadays many plugins have a broken source plugin.

Every such instance is worth a bug report. Either the import wizard is broken, or tycho produces broken meta data, or .... Either one should be fixed.

Quote:

Any suggestions on how it is now possible to add custom instrumentation to a platform plugin without struggling with the entire OOMPH of the platform?

I guess oomphing the entire platform is mainly a problem of the sheer mass of stuff. Other than that, importing through the wizard and oomph are the solutions, looking for still more alternatives is unlikely to find a more comprehensive and better tested approach.

HTH,
Stephan

Re: Horrible Lag [message #1799222 is a reply to message #1798355]

Sun, 02 December 2018 13:49

Eclipse User

To me, the latest usable Eclipse release is Oxygen.3a Release (4.7.3a).

I've tried Photon and SimRel-201809, and switched among these 3 releases for quite some time. The Photon and SimRel releases are good for about half an hour after fresh start; after the embedded tomcat server is started and few code changes are hot swapped/deployed to the running tomcat server, Photon and SimRel becomes unusable; only Oxygen remains reasonable.

So now, I stick with Oxygen; and waiting to see how the next SimRel release turns out.

By the way, I'm on Windows 10 and Jdk 8.

Re: Horrible Lag [message #1799224 is a reply to message #1799222]

Sun, 02 December 2018 14:14

Eclipse User

@harry, we would like to help, either by recommending workarounds or by fixing bugs, but with the given information neither is possible --- or wait: if it is really a problem relating to hotswapping into tomcat, perhaps the experts in the Webtools forum know more...

Other than that, everyone who observes these problems could be the hero providing the information necessary for improving Eclipse.
See previous comments for hints on how to collect useful information.

Previous Topic:	Is changing of current-line color and current-item color broken?
Next Topic:	Unable to connect to repository http://download.eclipse.org/webtools/repository/neon/compositeConten

Goto Forum:

-=] Back to Top [=-

Current Time: Mon Jul 14 14:42:19 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter