Eclipse Community Forums: ServerTools (WTP) » Eclipse 3.1.1 WDT 1.0 are too slow...

Home » Language IDEs » ServerTools (WTP) » Eclipse 3.1.1 WDT 1.0 are too slow...

Eclipse 3.1.1 WDT 1.0 are too slow... [message #158180]

Fri, 27 January 2006 13:59

Eclipse User

Originally posted by: p.panconi.gmail.com

I passed to Eclipse 3.1.1 with WDT 1.0... but it's really impossibile to
use them... all it's too slow... when we save a file all froze and It need
same second to free up.

Why .deployables was removed? Now the compiling heve to generate bytecode
and publish to the direcory .metainfo/.../... /tmp0/... It semas relly to
much heavy...

I'm really sad of this new bad surprise... I thic Ill pass to Sun Java
Studio.

Re: Eclipse 3.1.1 WDT 1.0 are too slow... [message #158436 is a reply to message #158180]

Mon, 30 January 2006 10:16

Eclipse User

Originally posted by: caclark.etechsolutions.net

Paul Panks said the following on 1/27/2006 12:59 PM:
> I passed to Eclipse 3.1.1 with WDT 1.0... but it's really impossibile to
> use them... all it's too slow... when we save a file all froze and It
> need same second to free up.
>
> Why .deployables was removed? Now the compiling heve to generate
> bytecode and publish to the direcory .metainfo/.../... /tmp0/... It
> semas relly to much heavy...
>
> I'm really sad of this new bad surprise... I thic Ill pass to Sun Java
> Studio.
>

Well, perhaps you could spend some time searching this newsgroup. It's
well documented what the issues were. They've been resolved in the
first maintenance release. The .deployables disappearing is not an
issue. It's purpose was exactly as you described in publishing to the
tmpX directory, so it's 6 of one, half a dozen of the other.

Re: Eclipse 3.1.1 WDT 1.0 are too slow... [message #158573 is a reply to message #158180]

Tue, 31 January 2006 07:47

Eclipse User

Originally posted by: alex_blewitt.yahoo.com

The application being slow could well be a function of your environment, not of the software. If your hard-drive light is permanently on, then that's an indication that it's thrashing and performance will nose-dive.

There was a few bug reports of minor lock-ups occuring when a System.gc() call happened; it's something that can be disabled by putting idle.gc=false in the Eclipse.ini parameters. However, that bug was tracked down to an issue with the Sun VM in 1.5; so if you've got a Java 1.5 then I suggest that you update it to the latest and greatest.

Alex.

Previous Topic:	Steps To Creating A Custom Server Runtime
Next Topic:	WTP 1.0 and Tomcat classpath

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Mar 19 09:47:27 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter