Eclipse Community Forums: Eclipse Platform » Ganymede M6 startup slow?

Help

Home

Home » Eclipse Projects » Eclipse Platform » Ganymede M6 startup slow?

Show: Today's Messages :: Show Polls :: Message Navigator

Ganymede M6 startup slow? [message #327253]

Mon, 14 April 2008 16:23

Eclipse User

Originally posted by: eclipse-news.rizzoweb.com

HAs anyone else experienced very slow startup using Ganyemede (Eclipse
3.4M6)?

Eclipse Build id: I20080330-1350
Windows XP, nearly new dual-core processor, 2GB RAM
Sun JDK 1.5

I downloaded one of the EPP packages I-builds to get Ganymede M6.
When I start Eclipse, it takes 30-40 seconds just to show the workspace
selection dialog. Once I select a workspace, it takes about 10 seconds
to show the Workbench and then another ~20 seconds for Initializing Java
Tooling job to complete. This happens even when I have just shut down
Eclipse to restart it.

3.3 on the same machine using same JVM is significantly faster.

Anyone else experience such a drastic startup slowdowns compared to 3.3?

Eric

Report message to a moderator

Re: Ganymede M6 startup slow? [message #327257 is a reply to message #327253]

Mon, 14 April 2008 19:21

Mark Melvin

Messages: 118
Registered: July 2009

Senior Member

Hi Eric,

I have noticed the same thing. I noticed the splash screen takes a
now-noticable amount of time to appear as well. I recall one advantage of
the Eclipse 3.3 startup mechanism re-work was to have an almost immediate
splash screen, but something appears to be undoing that. I too found that
the time for the workspace selection to appear, as well as the
post-workspace selection to "workbench is up" time both seem to have
noticably increased (versus 3.3) on my machine as well. I have not
attempted to narrow it down yet, but I kind of assumed it was a known
issue and perhaps something to do with p2.

Mark.

On Mon, 14 Apr 2008 12:23:04 -0400, Eric Rizzo <eclipse-news@rizzoweb.com>
wrote:

> HAs anyone else experienced very slow startup using Ganyemede (Eclipse
> 3.4M6)?
>
> Eclipse Build id: I20080330-1350
> Windows XP, nearly new dual-core processor, 2GB RAM
> Sun JDK 1.5
>
> I downloaded one of the EPP packages I-builds to get Ganymede M6.
> When I start Eclipse, it takes 30-40 seconds just to show the workspace
> selection dialog. Once I select a workspace, it takes about 10 seconds
> to show the Workbench and then another ~20 seconds for Initializing Java
> Tooling job to complete. This happens even when I have just shut down
> Eclipse to restart it.
>
> 3.3 on the same machine using same JVM is significantly faster.
>
> Anyone else experience such a drastic startup slowdowns compared to 3.3?
>
> Eric

Report message to a moderator

Re: Ganymede M6 startup slow? [message #327288 is a reply to message #327253]

Tue, 15 April 2008 10:21

Eclipse User

Originally posted by: groups.pellaton.li

Hi

Yes, I did experience the slowdown too - with all additional plug-ins we
are using (WTP, SVN, CheckStyle, EclEmma, SpringIDE, ...) it took up to
8 (eight) minutes to start Eclipse 3.4.M6a compared to a few seconds in
3.3.2.

The new provisioning called "p2" is causing all the delays:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=224269
https://bugs.eclipse.org/bugs/show_bug.cgi?id=224579
https://bugs.eclipse.org/bugs/show_bug.cgi?id=224658
....

As I don't need the features of p2, I removed it as described here

http://wiki.eclipse.org/Equinox_p2_Removal

Since doing so, the startup is back to "normal" durations.

Hope this helps

Michael Pellaton

Report message to a moderator

Re: Ganymede M6 startup slow? [message #327364 is a reply to message #327288]

Wed, 16 April 2008 15:53

Eclipse User

Originally posted by: eclipse-news.rizzoweb.com

Michael Pellaton wrote:
> Hi
>
> Yes, I did experience the slowdown too - with all additional plug-ins we
> are using (WTP, SVN, CheckStyle, EclEmma, SpringIDE, ...) it took up to
> 8 (eight) minutes to start Eclipse 3.4.M6a compared to a few seconds in
> 3.3.2.
>
> The new provisioning called "p2" is causing all the delays:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=224269
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=224579
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=224658

Thanks for those references - it definitely sounds like the root of the
problems I'm seeing. For other reasons, our team typically runs with
-clean in our eclipse.ini all the time, so I'm likely bumping into this
issue harder than most people since p2 is constantly re-reading
everything every time I start.

Eric

Report message to a moderator

Previous Topic:	How to use CVS to get org.eclipse.releng.*
Next Topic:	Compiling Eclipse Code

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sun Jul 07 06:31:55 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter