Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » IAM (Eclipse Integration for Apache Maven) » IAM installation results in extremely slow Eclipse startup
IAM installation results in extremely slow Eclipse startup [message #14266] Fri, 07 November 2008 18:11 Go to next message
Anthony Whyte is currently offline Anthony WhyteFriend
Messages: 2
Registered: July 2009
Junior Member
I'm at ApacheCon 08 and after attending the IAM presentation I thought I'd
add the plugin to my Eclipse Version: 3.3.2 Build id: M20080221-1800
running on my MacBook Pro laptop. Plugin installation was successful but
now Eclipse takes several minutes to start up and display the workplace
selection dialog. Any suggestions as to how to tune the startup process
for a more normal startup?
Re: IAM installation results in extremely slow Eclipse startup [message #14287 is a reply to message #14266] Sat, 08 November 2008 16:12 Go to previous messageGo to next message
Abel Mui is currently offline Abel MuiFriend
Messages: 247
Registered: July 2009
Senior Member
Anthony Whyte wrote:

> now Eclipse takes several minutes to start up and display the workplace
> selection dialog. Any suggestions as to how to tune the startup process
> for a more normal startup?

This is the first time we get such a report. IAM does nothing special
during eclipse startup, but you might want to open a bugzilla with the log
files for eclipse so we can look for something suspicious.

For reference, I use it on both an iMac and MacBook (both intel based), as
well as Windows and have noticed no delays on startup.

--
Abel Muiño
Re: IAM installation results in extremely slow Eclipse startup [message #14304 is a reply to message #14287] Mon, 10 November 2008 08:45 Go to previous messageGo to next message
Dave Syer is currently offline Dave SyerFriend
Messages: 95
Registered: July 2009
Member
That's pretty surprising, given that there are quite a few bug reports
on the Q4E googlecode issue tracker relating to slow start up (there is
a relationship there right?). IAM in general is very slow in a large
workspace, especially if there are snapshot dependencies.

Sometimes it takes nearly an hour for Eclipse to start up in my case.

Abel Muiño wrote:
> This is the first time we get such a report. IAM does nothing special
> during eclipse startup, but you might want to open a bugzilla with the
> log files for eclipse so we can look for something suspicious.
>
> For reference, I use it on both an iMac and MacBook (both intel based),
> as well as Windows and have noticed no delays on startup.
>
> --
> Abel Muiño
>
>
Re: IAM installation results in extremely slow Eclipse startup [message #14321 is a reply to message #14304] Mon, 10 November 2008 14:13 Go to previous messageGo to next message
Abel Mui is currently offline Abel MuiFriend
Messages: 247
Registered: July 2009
Senior Member
Hello Dave,

If I understood the original question, it was reporting a long delay to
display the workspace selection dialog (that is, before opening any
workspace).

This is not related to other performance reports in q4e issue tracker,
since those reports are about performance on large workspaces.

We are actively working on performance, by the way.

Dave Syer wrote:

> That's pretty surprising, given that there are quite a few bug reports
> on the Q4E googlecode issue tracker relating to slow start up (there is
> a relationship there right?). IAM in general is very slow in a large
> workspace, especially if there are snapshot dependencies.

> Sometimes it takes nearly an hour for Eclipse to start up in my case.

> Abel Muiño wrote:
>> This is the first time we get such a report. IAM does nothing special
>> during eclipse startup, but you might want to open a bugzilla with the
>> log files for eclipse so we can look for something suspicious.
>>
>> For reference, I use it on both an iMac and MacBook (both intel based),
>> as well as Windows and have noticed no delays on startup.
>>
>> --
>> Abel Muiño
>>
>>
Re: IAM installation results in extremely slow Eclipse startup [message #14332 is a reply to message #14321] Mon, 10 November 2008 14:57 Go to previous messageGo to next message
Dave Syer is currently offline Dave SyerFriend
Messages: 95
Registered: July 2009
Member
Abel,

Thanks for the update. Maybe I missed the point of the original post.
Is the Q4E issue tracker going to be ported over to Eclipse bugzilla, by
the way? It's very confusing having two places to track issues.

Dave.

> Hello Dave,
> If I understood the original question, it was reporting a long delay to
> display the workspace selection dialog (that is, before opening any
> workspace).
>
> This is not related to other performance reports in q4e issue tracker,
> since those reports are about performance on large workspaces.
>
> We are actively working on performance, by the way.
>
> Dave Syer wrote:
>
Moving q4e issues to bugzilla? [message #15758 is a reply to message #14332] Wed, 12 November 2008 21:37 Go to previous messageGo to next message
Abel Mui is currently offline Abel MuiFriend
Messages: 247
Registered: July 2009
Senior Member
Hi Dave,

I agree that it would be much better to have all issues in a single place,
so you get my +1 for moving the tickets in q4e's tracker to bugzilla.

Some issues were already moved by committers (specially those related to
the pom editor), but this is a topic where community participation can
make the difference. It would be of great help if interested parties could
move their favorite bugs and close them as "Moved-to-IAM" in q4e's tracker
(I've just created that state).

Thanks!
Abel Muiño.

Dave Syer wrote:

> Is the Q4E issue tracker going to be ported over to Eclipse bugzilla, by
> the way? It's very confusing having two places to track issues.
Re: Moving q4e issues to bugzilla? [message #15785 is a reply to message #15758] Thu, 13 November 2008 08:41 Go to previous messageGo to next message
Dave Syer is currently offline Dave SyerFriend
Messages: 95
Registered: July 2009
Member
Abel Muiño wrote:
> Some issues were already moved by committers (specially those related to
> the pom editor), but this is a topic where community participation can
> make the difference. It would be of great help if interested parties
> could move their favorite bugs and close them as "Moved-to-IAM" in q4e's
> tracker (I've just created that state).

Only the committers have permission to close issues? Can't you automate
the process somehow? At least put a message on the Q4E home page saying
that the issue tracker is not in use?
Re: Moving q4e issues to bugzilla? [message #15841 is a reply to message #15785] Thu, 13 November 2008 16:30 Go to previous message
Abel Mui is currently offline Abel MuiFriend
Messages: 247
Registered: July 2009
Senior Member
Hi Dave,
I'm not sure if non-committers can close issues at google... I can't find
a way to configure that.

We need to make more obvious that the q4e site is "closing". It is not
actually useless, since the embedder bundles will be generated on
googlecode for a while.

Thanks!
Abel Muiño

Dave Syer wrote:

> Abel Muiño wrote:
>> Some issues were already moved by committers (specially those related to
>> the pom editor), but this is a topic where community participation can
>> make the difference. It would be of great help if interested parties
>> could move their favorite bugs and close them as "Moved-to-IAM" in q4e's
>> tracker (I've just created that state).

> Only the committers have permission to close issues? Can't you automate
> the process somehow? At least put a message on the Q4E home page saying
> that the issue tracker is not in use?
Re: IAM installation results in extremely slow Eclipse startup [message #567727 is a reply to message #14266] Sat, 08 November 2008 16:12 Go to previous message
Abel Mui is currently offline Abel MuiFriend
Messages: 247
Registered: July 2009
Senior Member
Anthony Whyte wrote:

> now Eclipse takes several minutes to start up and display the workplace
> selection dialog. Any suggestions as to how to tune the startup process
> for a more normal startup?

This is the first time we get such a report. IAM does nothing special
during eclipse startup, but you might want to open a bugzilla with the log
files for eclipse so we can look for something suspicious.

For reference, I use it on both an iMac and MacBook (both intel based), as
well as Windows and have noticed no delays on startup.

--
Abel Muiño
Re: IAM installation results in extremely slow Eclipse startup [message #567756 is a reply to message #14287] Mon, 10 November 2008 08:45 Go to previous message
Dave Syer is currently offline Dave SyerFriend
Messages: 95
Registered: July 2009
Member
That's pretty surprising, given that there are quite a few bug reports
on the Q4E googlecode issue tracker relating to slow start up (there is
a relationship there right?). IAM in general is very slow in a large
workspace, especially if there are snapshot dependencies.

Sometimes it takes nearly an hour for Eclipse to start up in my case.

Abel Muiño wrote:
> This is the first time we get such a report. IAM does nothing special
> during eclipse startup, but you might want to open a bugzilla with the
> log files for eclipse so we can look for something suspicious.
>
> For reference, I use it on both an iMac and MacBook (both intel based),
> as well as Windows and have noticed no delays on startup.
>
> --
> Abel Muiño
>
>
Re: IAM installation results in extremely slow Eclipse startup [message #567787 is a reply to message #14304] Mon, 10 November 2008 14:13 Go to previous message
Abel Mui is currently offline Abel MuiFriend
Messages: 247
Registered: July 2009
Senior Member
Hello Dave,

If I understood the original question, it was reporting a long delay to
display the workspace selection dialog (that is, before opening any
workspace).

This is not related to other performance reports in q4e issue tracker,
since those reports are about performance on large workspaces.

We are actively working on performance, by the way.

Dave Syer wrote:

> That's pretty surprising, given that there are quite a few bug reports
> on the Q4E googlecode issue tracker relating to slow start up (there is
> a relationship there right?). IAM in general is very slow in a large
> workspace, especially if there are snapshot dependencies.

> Sometimes it takes nearly an hour for Eclipse to start up in my case.

> Abel Muiño wrote:
>> This is the first time we get such a report. IAM does nothing special
>> during eclipse startup, but you might want to open a bugzilla with the
>> log files for eclipse so we can look for something suspicious.
>>
>> For reference, I use it on both an iMac and MacBook (both intel based),
>> as well as Windows and have noticed no delays on startup.
>>
>> --
>> Abel Muiño
>>
>>
Re: IAM installation results in extremely slow Eclipse startup [message #567814 is a reply to message #14321] Mon, 10 November 2008 14:57 Go to previous message
Dave Syer is currently offline Dave SyerFriend
Messages: 95
Registered: July 2009
Member
Abel,

Thanks for the update. Maybe I missed the point of the original post.
Is the Q4E issue tracker going to be ported over to Eclipse bugzilla, by
the way? It's very confusing having two places to track issues.

Dave.

> Hello Dave,
> If I understood the original question, it was reporting a long delay to
> display the workspace selection dialog (that is, before opening any
> workspace).
>
> This is not related to other performance reports in q4e issue tracker,
> since those reports are about performance on large workspaces.
>
> We are actively working on performance, by the way.
>
> Dave Syer wrote:
>
Moving q4e issues to bugzilla? [message #567841 is a reply to message #14332] Wed, 12 November 2008 21:37 Go to previous message
Abel Mui is currently offline Abel MuiFriend
Messages: 247
Registered: July 2009
Senior Member
Hi Dave,

I agree that it would be much better to have all issues in a single place,
so you get my +1 for moving the tickets in q4e's tracker to bugzilla.

Some issues were already moved by committers (specially those related to
the pom editor), but this is a topic where community participation can
make the difference. It would be of great help if interested parties could
move their favorite bugs and close them as "Moved-to-IAM" in q4e's tracker
(I've just created that state).

Thanks!
Abel Muiño.

Dave Syer wrote:

> Is the Q4E issue tracker going to be ported over to Eclipse bugzilla, by
> the way? It's very confusing having two places to track issues.
Re: Moving q4e issues to bugzilla? [message #567906 is a reply to message #15758] Thu, 13 November 2008 08:41 Go to previous message
Dave Syer is currently offline Dave SyerFriend
Messages: 95
Registered: July 2009
Member
Abel Muiño wrote:
> Some issues were already moved by committers (specially those related to
> the pom editor), but this is a topic where community participation can
> make the difference. It would be of great help if interested parties
> could move their favorite bugs and close them as "Moved-to-IAM" in q4e's
> tracker (I've just created that state).

Only the committers have permission to close issues? Can't you automate
the process somehow? At least put a message on the Q4E home page saying
that the issue tracker is not in use?
Re: Moving q4e issues to bugzilla? [message #567981 is a reply to message #15785] Thu, 13 November 2008 16:30 Go to previous message
Abel Mui is currently offline Abel MuiFriend
Messages: 247
Registered: July 2009
Senior Member
Hi Dave,
I'm not sure if non-committers can close issues at google... I can't find
a way to configure that.

We need to make more obvious that the q4e site is "closing". It is not
actually useless, since the embedder bundles will be generated on
googlecode for a while.

Thanks!
Abel Muiño

Dave Syer wrote:

> Abel Muiño wrote:
>> Some issues were already moved by committers (specially those related to
>> the pom editor), but this is a topic where community participation can
>> make the difference. It would be of great help if interested parties
>> could move their favorite bugs and close them as "Moved-to-IAM" in q4e's
>> tracker (I've just created that state).

> Only the committers have permission to close issues? Can't you automate
> the process somehow? At least put a message on the Q4E home page saying
> that the issue tracker is not in use?
Previous Topic:packaging problem
Next Topic:packaging problem
Goto Forum:
  


Current Time: Sat Dec 20 21:48:41 GMT 2014

Powered by FUDForum. Page generated in 0.04692 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software