Home » Language IDEs » AspectJ » Isn't it too slow after using AJDT plugin?
Isn't it too slow after using AJDT plugin? [message #44501] |
Wed, 24 November 2004 02:46 |
Eclipse User |
|
|
|
Originally posted by: only4hj.softforum.com
I'm using AJDT 1.1.12 and Eclipse 3.0
Before I started using AJDT, it was OK.
But, after using that, my Eclipse got too slow.
It took too much time to compile projects I made before and had no AspectJ
files.
It seems that every work in Eclipse happens to take too much time after AJDT
installation.
I can't do anything with this slow Eclipse.
Are there any settings I can try?
Thanks.
|
|
| | |
Re: Isn't it too slow after using AJDT plugin? [message #44596 is a reply to message #44567] |
Fri, 26 November 2004 02:19 |
Eclipse User |
|
|
|
Originally posted by: only4hj.softforum.com
Thanks guys.
I've checked "Use incremental compilation" option and am using Default Java
Editor for *.java files.
Things are getting better. But I still have two problems.
One.
It takes long time when I close and open projects.
When I open or close a project, even though the project is not a AspectJ
project nor has no reference to
any AspectJ projects, it takes one minute or so.
When closing a project, a progress box shows up and says 'Operation in
process..', progress bar reaches to the end
and takes a whole CPU.
Two.
When I save a file with incremental build and automatic build turned on, it
consumes 100% CPU for 7 seconds
and Progress shows that 'Invoking Aspect Builder on /MyProject.'.
Even though the file I modified is not in build.ajproperties, it seems that
Aspect Builder does something.
There was no defference whether checking "Use incremental compilation" or
not.
My machine is Pentium IV 2.4 GHz, Windows XP.
Thanks.
"Guillaume Pothier" <gpothier@free.fr> wrote in message
news:co5696$6rn$1@www.eclipse.org...
> If you mean that java file edition is slower for non-AspectJ projects, it
> might be that the platform is set up to open java files with the AjpectJ
> editor.
> Check that in the preferences/workbench/file associations page.
>
> Matthew Webster wrote:
>> Dae-Joong wrote:
>>
>> I assume you mean that your AspectJ projects and any projects that depend
>> upon them now take a long time to rebuild. The reason for this is that by
>> default AJDT does a complete build of your project when you save a file.
>> To change this check the "Use incremental compilation" option on the
>> "AspectJ" page of the project properties (see 1.1.12 documentation on
>> http://eclipse.org/ajdt/). A full build will still occur when changing
>> aspects.
>>
>>> I'm using AJDT 1.1.12 and Eclipse 3.0
>>
>>
>>> Before I started using AJDT, it was OK.
>>> But, after using that, my Eclipse got too slow.
>>
>>
>>> It took too much time to compile projects I made before and had no
>>> AspectJ files.
>>> It seems that every work in Eclipse happens to take too much time after
>>> AJDT installation.
>>
>>
>>> I can't do anything with this slow Eclipse.
>>
>>
>>> Are there any settings I can try?
>>
>>
>>> Thanks.
>>
>>
|
|
|
Re: Isn't it too slow after using AJDT plugin? [message #44627 is a reply to message #44596] |
Fri, 26 November 2004 11:42 |
Guillaume Pothier Messages: 107 Registered: July 2009 |
Senior Member |
|
|
Sounds like a bug. I remember there has been an issue some time ago with
builds that would trigger without logical cause...
Dae-Joong wrote:
> Thanks guys.
>
> I've checked "Use incremental compilation" option and am using Default Java
> Editor for *.java files.
>
> Things are getting better. But I still have two problems.
>
> One.
>
> It takes long time when I close and open projects.
>
> When I open or close a project, even though the project is not a AspectJ
> project nor has no reference to
> any AspectJ projects, it takes one minute or so.
> When closing a project, a progress box shows up and says 'Operation in
> process..', progress bar reaches to the end
> and takes a whole CPU.
>
> Two.
>
> When I save a file with incremental build and automatic build turned on, it
> consumes 100% CPU for 7 seconds
> and Progress shows that 'Invoking Aspect Builder on /MyProject.'.
> Even though the file I modified is not in build.ajproperties, it seems that
> Aspect Builder does something.
>
> There was no defference whether checking "Use incremental compilation" or
> not.
>
> My machine is Pentium IV 2.4 GHz, Windows XP.
>
> Thanks.
>
>
> "Guillaume Pothier" <gpothier@free.fr> wrote in message
> news:co5696$6rn$1@www.eclipse.org...
>
>>If you mean that java file edition is slower for non-AspectJ projects, it
>>might be that the platform is set up to open java files with the AjpectJ
>>editor.
>>Check that in the preferences/workbench/file associations page.
>>
>>Matthew Webster wrote:
>>
>>>Dae-Joong wrote:
>>>
>>>I assume you mean that your AspectJ projects and any projects that depend
>>>upon them now take a long time to rebuild. The reason for this is that by
>>>default AJDT does a complete build of your project when you save a file.
>>>To change this check the "Use incremental compilation" option on the
>>>"AspectJ" page of the project properties (see 1.1.12 documentation on
>>>http://eclipse.org/ajdt/). A full build will still occur when changing
>>>aspects.
>>>
>>>
>>>>I'm using AJDT 1.1.12 and Eclipse 3.0
>>>
>>>
>>>>Before I started using AJDT, it was OK.
>>>>But, after using that, my Eclipse got too slow.
>>>
>>>
>>>>It took too much time to compile projects I made before and had no
>>>>AspectJ files.
>>>>It seems that every work in Eclipse happens to take too much time after
>>>>AJDT installation.
>>>
>>>
>>>>I can't do anything with this slow Eclipse.
>>>
>>>
>>>>Are there any settings I can try?
>>>
>>>
>>>>Thanks.
>>>
>>>
>
|
|
|
Re: Isn't it too slow after using AJDT plugin? [message #44686 is a reply to message #44627] |
Mon, 29 November 2004 08:40 |
Eclipse User |
|
|
|
Originally posted by: hawkinsh.uk.ibm.com
Guillaume Pothier wrote:
> Sounds like a bug. I remember there has been an issue some time ago with
> builds that would trigger without logical cause...
> Dae-Joong wrote:
>> Thanks guys.
>> Two.
>>
>> When I save a file with incremental build and automatic build turned on, it
>> consumes 100% CPU for 7 seconds
>> and Progress shows that 'Invoking Aspect Builder on /MyProject.'.
>> Even though the file I modified is not in build.ajproperties, it seems that
>> Aspect Builder does something.
>>
>> There was no defference whether checking "Use incremental compilation" or
>> not.
Hi. Yes, this is a bug. I'm hoping to have the fix in sometime today.
Thanks, Helen
|
|
|
Re: Isn't it too slow after using AJDT plugin? [message #44913 is a reply to message #44596] |
Thu, 16 December 2004 14:03 |
Eclipse User |
|
|
|
Originally posted by: mchapman.uk.ibm.com
On Fri, 26 Nov 2004 11:19:15 +0900, Dae-Joong wrote:
> It takes long time when I close and open projects.
>
> When I open or close a project, even though the project is not a AspectJ
> project nor has no reference to
> any AspectJ projects, it takes one minute or so. When closing a project, a
> progress box shows up and says 'Operation in process..', progress bar
> reaches to the end and takes a whole CPU.
Hi,
This should be improved in AJDT 1.2.0M2. I managed to reduce the scope of
our resource change listener to avoid processing deltas for non-AspectJ
projects. I'm also going to ask the Eclipse team if there is a better
solution here, or whether one can be added in the future, because there
still seems to be an overhead in calling our listener, even if we do
nothing with the delta.
Regards,
Matt.
|
|
| | |
Re: Isn't it too slow after using AJDT plugin? [message #585104 is a reply to message #44567] |
Fri, 26 November 2004 02:19 |
Eclipse User |
|
|
|
Originally posted by: only4hj.softforum.com
Thanks guys.
I've checked "Use incremental compilation" option and am using Default Java
Editor for *.java files.
Things are getting better. But I still have two problems.
One.
It takes long time when I close and open projects.
When I open or close a project, even though the project is not a AspectJ
project nor has no reference to
any AspectJ projects, it takes one minute or so.
When closing a project, a progress box shows up and says 'Operation in
process..', progress bar reaches to the end
and takes a whole CPU.
Two.
When I save a file with incremental build and automatic build turned on, it
consumes 100% CPU for 7 seconds
and Progress shows that 'Invoking Aspect Builder on /MyProject.'.
Even though the file I modified is not in build.ajproperties, it seems that
Aspect Builder does something.
There was no defference whether checking "Use incremental compilation" or
not.
My machine is Pentium IV 2.4 GHz, Windows XP.
Thanks.
"Guillaume Pothier" <gpothier@free.fr> wrote in message
news:co5696$6rn$1@www.eclipse.org...
> If you mean that java file edition is slower for non-AspectJ projects, it
> might be that the platform is set up to open java files with the AjpectJ
> editor.
> Check that in the preferences/workbench/file associations page.
>
> Matthew Webster wrote:
>> Dae-Joong wrote:
>>
>> I assume you mean that your AspectJ projects and any projects that depend
>> upon them now take a long time to rebuild. The reason for this is that by
>> default AJDT does a complete build of your project when you save a file.
>> To change this check the "Use incremental compilation" option on the
>> "AspectJ" page of the project properties (see 1.1.12 documentation on
>> http://eclipse.org/ajdt/). A full build will still occur when changing
>> aspects.
>>
>>> I'm using AJDT 1.1.12 and Eclipse 3.0
>>
>>
>>> Before I started using AJDT, it was OK.
>>> But, after using that, my Eclipse got too slow.
>>
>>
>>> It took too much time to compile projects I made before and had no
>>> AspectJ files.
>>> It seems that every work in Eclipse happens to take too much time after
>>> AJDT installation.
>>
>>
>>> I can't do anything with this slow Eclipse.
>>
>>
>>> Are there any settings I can try?
>>
>>
>>> Thanks.
>>
>>
|
|
|
Re: Isn't it too slow after using AJDT plugin? [message #585113 is a reply to message #44596] |
Fri, 26 November 2004 11:42 |
Guillaume Pothier Messages: 107 Registered: July 2009 |
Senior Member |
|
|
Sounds like a bug. I remember there has been an issue some time ago with
builds that would trigger without logical cause...
Dae-Joong wrote:
> Thanks guys.
>
> I've checked "Use incremental compilation" option and am using Default Java
> Editor for *.java files.
>
> Things are getting better. But I still have two problems.
>
> One.
>
> It takes long time when I close and open projects.
>
> When I open or close a project, even though the project is not a AspectJ
> project nor has no reference to
> any AspectJ projects, it takes one minute or so.
> When closing a project, a progress box shows up and says 'Operation in
> process..', progress bar reaches to the end
> and takes a whole CPU.
>
> Two.
>
> When I save a file with incremental build and automatic build turned on, it
> consumes 100% CPU for 7 seconds
> and Progress shows that 'Invoking Aspect Builder on /MyProject.'.
> Even though the file I modified is not in build.ajproperties, it seems that
> Aspect Builder does something.
>
> There was no defference whether checking "Use incremental compilation" or
> not.
>
> My machine is Pentium IV 2.4 GHz, Windows XP.
>
> Thanks.
>
>
> "Guillaume Pothier" <gpothier@free.fr> wrote in message
> news:co5696$6rn$1@www.eclipse.org...
>
>>If you mean that java file edition is slower for non-AspectJ projects, it
>>might be that the platform is set up to open java files with the AjpectJ
>>editor.
>>Check that in the preferences/workbench/file associations page.
>>
>>Matthew Webster wrote:
>>
>>>Dae-Joong wrote:
>>>
>>>I assume you mean that your AspectJ projects and any projects that depend
>>>upon them now take a long time to rebuild. The reason for this is that by
>>>default AJDT does a complete build of your project when you save a file.
>>>To change this check the "Use incremental compilation" option on the
>>>"AspectJ" page of the project properties (see 1.1.12 documentation on
>>>http://eclipse.org/ajdt/). A full build will still occur when changing
>>>aspects.
>>>
>>>
>>>>I'm using AJDT 1.1.12 and Eclipse 3.0
>>>
>>>
>>>>Before I started using AJDT, it was OK.
>>>>But, after using that, my Eclipse got too slow.
>>>
>>>
>>>>It took too much time to compile projects I made before and had no
>>>>AspectJ files.
>>>>It seems that every work in Eclipse happens to take too much time after
>>>>AJDT installation.
>>>
>>>
>>>>I can't do anything with this slow Eclipse.
>>>
>>>
>>>>Are there any settings I can try?
>>>
>>>
>>>>Thanks.
>>>
>>>
>
|
|
|
Re: Isn't it too slow after using AJDT plugin? [message #585140 is a reply to message #44627] |
Mon, 29 November 2004 08:40 |
Eclipse User |
|
|
|
Originally posted by: hawkinsh.uk.ibm.com
Guillaume Pothier wrote:
> Sounds like a bug. I remember there has been an issue some time ago with
> builds that would trigger without logical cause...
> Dae-Joong wrote:
>> Thanks guys.
>> Two.
>>
>> When I save a file with incremental build and automatic build turned on, it
>> consumes 100% CPU for 7 seconds
>> and Progress shows that 'Invoking Aspect Builder on /MyProject.'.
>> Even though the file I modified is not in build.ajproperties, it seems that
>> Aspect Builder does something.
>>
>> There was no defference whether checking "Use incremental compilation" or
>> not.
Hi. Yes, this is a bug. I'm hoping to have the fix in sometime today.
Thanks, Helen
|
|
|
Re: Isn't it too slow after using AJDT plugin? [message #585252 is a reply to message #44596] |
Thu, 16 December 2004 14:03 |
Matt Chapman Messages: 429 Registered: July 2009 |
Senior Member |
|
|
On Fri, 26 Nov 2004 11:19:15 +0900, Dae-Joong wrote:
> It takes long time when I close and open projects.
>
> When I open or close a project, even though the project is not a AspectJ
> project nor has no reference to
> any AspectJ projects, it takes one minute or so. When closing a project, a
> progress box shows up and says 'Operation in process..', progress bar
> reaches to the end and takes a whole CPU.
Hi,
This should be improved in AJDT 1.2.0M2. I managed to reduce the scope of
our resource change listener to avoid processing deltas for non-AspectJ
projects. I'm also going to ask the Eclipse team if there is a better
solution here, or whether one can be added in the future, because there
still seems to be an overhead in calling our listener, even if we do
nothing with the delta.
Regards,
Matt.
|
|
|
Goto Forum:
Current Time: Mon Sep 23 09:25:01 GMT 2024
Powered by FUDForum. Page generated in 0.29768 seconds
|