Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » AspectJ » Super slow
Super slow [message #27270] Mon, 03 November 2003 01:52 Go to next message
Eclipse UserFriend
Originally posted by: wayne.williams.embarcadero.com

I am running Eclipse 3.0 on a decent box and performace is good. However
with the ajdt plugin it virtually grinds to a halt. With just a single
aspect file an aspectJ build will take at least 5 minutes.

My project is average size, about 1800 class files.

What performance expectations should I have? Is there anything I can do to
improve performance.

One thing I thought was I could reduce the scope of the aspectJ compile by
selecting about 10 classes in the default.lst file. Unfortunatly this
seemed to have no impact.

Regards,
---Wayne.
Re: Super slow [message #27306 is a reply to message #27270] Fri, 07 November 2003 17:41 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: clemas.uk.ibm.com

Hi Wayne,

1800 classes is a reasonable size project. I can think of a couple of
things that might help:

- Make sure that eclipse has enough memory to run. With the default, you
might not be getting OutOfMemory problems, but it could be Garbage
Collecting
itself to death. Try 'eclipse -vmargs -Xmx256M' to start it with more
memory.

- Don't edit the default.lst. Its a special .lst file that is generated
every time you click 'build' - it is always generated to contain all the
resources in your project. If you want to work with a subset of the
files, you should create a new .lst file using the new BuildConfiguration
wizard. We ought to hide the default.lst file so users don't try and
change it ...

does that help at all?

cheers,
Andy
AJDT Development.
Re: Super slow [message #27859 is a reply to message #27306] Tue, 11 November 2003 08:34 Go to previous message
Eclipse UserFriend
Originally posted by: wayne.williams.embarcadero.com

Hi Andy,

Thanks for the reply. I had tried both your suggestions, I should have =

included that in my original description. Unfortunatly they did not help=
.. =

I only resorted to modifying the default.lst when I could not get any =

performance benefit from a new .lst file. I have run eclipse with as muc=
h =

as half a gig and it made virtually no difference performance wise. When=
I =

ran with smaller heaps I did get OutOfMemory erros quite a bit.

It seems to be some strange interaction between AJDT and eclipse because=
I =

am able to build using the AspectJ browser in less than a minute but =

within eclipse it takes at least 7 times as long. I see great potential=
=

with aspects but the AJDT piece is really important IMHO to get the kind=
=

of development productivity we need for our project.

Regards,
---Wayne.

On Fri, 7 Nov 2003 17:41:40 +0000 (UTC), Andy Clement <clemas@uk.ibm.com=
> =

wrote:

> Hi Wayne,
>
> 1800 classes is a reasonable size project. I can think of a couple of=

> things that might help:
>
> - Make sure that eclipse has enough memory to run. With the default, =
you
> might not be getting OutOfMemory problems, but it could be Garbage
> Collecting
> itself to death. Try 'eclipse -vmargs -Xmx256M' to start it with more=

> memory.
>
> - Don't edit the default.lst. Its a special .lst file that is generat=
ed
> every time you click 'build' - it is always generated to contain all t=
he
> resources in your project. If you want to work with a subset of the
> files, you should create a new .lst file using the new BuildConfigurat=
ion
> wizard. We ought to hide the default.lst file so users don't try and
> change it ...
>
> does that help at all?
>
> cheers,
> Andy
> AJDT Development.
>



-- =

Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
Re: Super slow [message #572651 is a reply to message #27270] Fri, 07 November 2003 17:41 Go to previous message
Andrew Clement is currently offline Andrew ClementFriend
Messages: 162
Registered: July 2009
Senior Member
Hi Wayne,

1800 classes is a reasonable size project. I can think of a couple of
things that might help:

- Make sure that eclipse has enough memory to run. With the default, you
might not be getting OutOfMemory problems, but it could be Garbage
Collecting
itself to death. Try 'eclipse -vmargs -Xmx256M' to start it with more
memory.

- Don't edit the default.lst. Its a special .lst file that is generated
every time you click 'build' - it is always generated to contain all the
resources in your project. If you want to work with a subset of the
files, you should create a new .lst file using the new BuildConfiguration
wizard. We ought to hide the default.lst file so users don't try and
change it ...

does that help at all?

cheers,
Andy
AJDT Development.
Re: Super slow [message #572867 is a reply to message #27306] Tue, 11 November 2003 08:34 Go to previous message
Wayne Williams is currently offline Wayne WilliamsFriend
Messages: 4
Registered: July 2009
Junior Member
Hi Andy,

Thanks for the reply. I had tried both your suggestions, I should have =

included that in my original description. Unfortunatly they did not help=
.. =

I only resorted to modifying the default.lst when I could not get any =

performance benefit from a new .lst file. I have run eclipse with as muc=
h =

as half a gig and it made virtually no difference performance wise. When=
I =

ran with smaller heaps I did get OutOfMemory erros quite a bit.

It seems to be some strange interaction between AJDT and eclipse because=
I =

am able to build using the AspectJ browser in less than a minute but =

within eclipse it takes at least 7 times as long. I see great potential=
=

with aspects but the AJDT piece is really important IMHO to get the kind=
=

of development productivity we need for our project.

Regards,
---Wayne.

On Fri, 7 Nov 2003 17:41:40 +0000 (UTC), Andy Clement <clemas@uk.ibm.com=
> =

wrote:

> Hi Wayne,
>
> 1800 classes is a reasonable size project. I can think of a couple of=

> things that might help:
>
> - Make sure that eclipse has enough memory to run. With the default, =
you
> might not be getting OutOfMemory problems, but it could be Garbage
> Collecting
> itself to death. Try 'eclipse -vmargs -Xmx256M' to start it with more=

> memory.
>
> - Don't edit the default.lst. Its a special .lst file that is generat=
ed
> every time you click 'build' - it is always generated to contain all t=
he
> resources in your project. If you want to work with a subset of the
> files, you should create a new .lst file using the new BuildConfigurat=
ion
> wizard. We ought to hide the default.lst file so users don't try and
> change it ...
>
> does that help at all?
>
> cheers,
> Andy
> AJDT Development.
>



-- =

Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
Previous Topic:AJDT in WSAD5.0.1: compile failed
Next Topic:Showing
Goto Forum:
  


Current Time: Tue Mar 19 08:46:45 GMT 2024

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

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

Back to the top