Home » Language IDEs » AspectJ » AJDT is slow
| AJDT is slow [message #60353] |
Tue, 10 January 2006 11:11  |
Eclipse User |
|
|
|
Originally posted by: scheglov_ke.nlmk.ru
I have several performance related questions.
1. What is AJDE and why is it so slow? See log log from "AJDT Event
Trace" below.
2. Is it true, that if I have one project (p1) with aspects (and classes
that should be processed) and other project (p2) that _uses_ processed
classes, then p2 should be also AJDT project? I know, that I don't need
"around", only "before" and "after".
3. Damn, in p1 I have _one_ aspect and _two_ beans that should be
processed. And right now it takes almost _6_ seconds to compile such
trivial case?! I use 256 Mb for Eclipse, so I think that memory is not
problem.
No, I am not negative, I like AJDT a lot, it is convinient, but so
slow... :-(
--------
13:51:35
============================================================ ===============================
13:51:35 Build kind = AUTOBUILD
13:51:35 Project=ru.nlmk.lab.admin.ui kind of build requested
=Incremental AspectJ compilation
13:51:35 build: Examined delta - source file changes in required
project ru.nlmk.lab.admin.ui
13:51:41 Timer event: 5689ms: Time to first compiled message
13:51:41 Timer event: 5699ms: Time to first woven message
13:51:41 AspectJ reports build successful, build was: INCREMENTAL
13:51:41 Timer event: 5779ms: Total time spent in AJDE
13:51:41 Timer event: 20ms: Create element map (0 rels in project:
ru.nlmk.lab.admin.ui)
13:51:41 Types affected during build = 1
13:51:41 Timer event: 0ms: Add markers (0 markers)
13:51:41 Timer event: 5959ms: Total time spent in AJBuilder.build()
--------
--
SY, Konstantin.
Advanced Eclipse SWT Designer (http://www.swt-designer.com)
|
|
|
| Re: AJDT is slow [message #60377 is a reply to message #60353] |
Tue, 10 January 2006 12:50  |
| Eclipse User |
|
|
|
Originally posted by: clemas.uk.ibm.com
Konstantin Scheglov wrote:
>
> I have several performance related questions.
>
> 1. What is AJDE and why is it so slow? See log log from "AJDT Event
> Trace" below.
AJDE is the AspectJ compiler itself which is called by the AJDT builder.
It is slower than a regular java compile because of the necessary
pointcut matching and weaving that has to occur for aspects.
*However* if you modify a single java class and save it, the subsequent
incremental compilation should take no more than 1 second.
>
> 2. Is it true, that if I have one project (p1) with aspects (and classes
> that should be processed) and other project (p2) that _uses_ processed
> classes, then p2 should be also AJDT project? I know, that I don't need
> "around", only "before" and "after".
Nope, project (p2) doesn't have to be an AJDT project if it simply
refers to classes from p1 - provided you aren't expecting the aspects
from project (p1) to affect project (p2).
>
> 3. Damn, in p1 I have _one_ aspect and _two_ beans that should be
> processed. And right now it takes almost _6_ seconds to compile such
> trivial case?! I use 256 Mb for Eclipse, so I think that memory is not
> problem.
Personally, I run -Xmx768M for eclipse. In the case you describe, (1
aspect, 2 beans) you should see sub-second compiles. As an experiment,
can you try it with more memory, 512M?
Andy.
|
|
|
| Re: AJDT is slow [message #60423 is a reply to message #60377] |
Wed, 11 January 2006 06:22 |
| Eclipse User |
|
|
|
Originally posted by: scheglov_ke.nlmk.ru
Andy Clement wrote:
>> I have several performance related questions.
>>
>> 1. What is AJDE and why is it so slow? See log log from "AJDT Event
>> Trace" below.
>
>
> AJDE is the AspectJ compiler itself which is called by the AJDT builder.
> It is slower than a regular java compile because of the necessary
> pointcut matching and weaving that has to occur for aspects.
>
> *However* if you modify a single java class and save it, the subsequent
> incremental compilation should take no more than 1 second.
Now I've changed to use separate workspace with only my current
projects (plugins, because I work on RCP). I am only in beginning, so
these projects are small:
1. ru.nlmk.libraries.external - with pile of jar's;
2. ru.nlmk.lab.core - core plugin with beans and aspect;
3. ru.nlmk.lab.admin.ui - currently only UI plugin that uses core;
4. ru.nlmk.lab.admin.application - application for RCP;
5. org.eclipse.jface.databinding - source snapshot of data binding
project (for fixing bug that present in 3.2M4).
Note, that I use Eclipse 3.1.1 (only bindings from 3.2M4).
JDT works very fast, I can see only short flashing of progress in
bottom right corner.
>> 2. Is it true, that if I have one project (p1) with aspects (and
>> classes that should be processed) and other project (p2) that _uses_
>> processed classes, then p2 should be also AJDT project? I know, that I
>> don't need "around", only "before" and "after".
>
>
> Nope, project (p2) doesn't have to be an AJDT project if it simply
> refers to classes from p1 - provided you aren't expecting the aspects
> from project (p1) to affect project (p2).
When (p2) is just Java project I have following error:
Severity Description Resource In Folder Location Creation Time Id
2 The project cannot be built until its prerequisite ru.nlmk.lab.core is
built. Cleaning and building all projects is recommended
ru.nlmk.lab.admin.ui January 11, 2006 9:00:35 AM 926
No matter, how much I do clear and rebuild, I still have this error.
I saw in google also same error for ANT building where was comment,
that _all_ projects referencing on ANT builded projects should be also
ANT builded. So, it seems that with AJDT I have same problem.
>> 3. Damn, in p1 I have _one_ aspect and _two_ beans that should be
>> processed. And right now it takes almost _6_ seconds to compile such
>> trivial case?! I use 256 Mb for Eclipse, so I think that memory is not
>> problem.
>
>
> Personally, I run -Xmx768M for eclipse. In the case you describe, (1
> aspect, 2 beans) you should see sub-second compiles. As an experiment,
> can you try it with more memory, 512M?
With separate workspace and 512M situation is a little better, but
still slow.
9:06:26 AM
============================================================ ===============================
9:06:26 AM Build kind = AUTOBUILD
9:06:26 AM Project=ru.nlmk.lab.core kind of build requested
=Incremental AspectJ compilation
9:06:26 AM build: Examined delta - source file changes in required
project ru.nlmk.lab.core
9:06:27 AM Timer event: 1102ms: Time to first compiled message
9:06:27 AM Timer event: 1192ms: Time to first woven message
9:06:27 AM AspectJ reports build successful, build was: INCREMENTAL
9:06:27 AM Timer event: 1242ms: Total time spent in AJDE
9:06:28 AM Timer event: 30ms: Create element map (34 rels in project:
ru.nlmk.lab.core)
9:06:28 AM Types affected during build = 1
9:06:28 AM Timer event: 0ms: Add markers (11 markers)
9:06:28 AM Timer event: 1612ms: Total time spent in AJBuilder.build()
--
SY, Konstantin.
Advanced Eclipse SWT Designer (http://www.swt-designer.com)
|
|
|
| Re: AJDT is slow [message #60446 is a reply to message #60423] |
Wed, 11 January 2006 09:15 |
| Eclipse User |
|
|
|
Originally posted by: clemas.uk.ibm.com
Konstantin Scheglov wrote:
>>> 2. Is it true, that if I have one project (p1) with aspects (and
>>> classes that should be processed) and other project (p2) that _uses_
>>> processed classes, then p2 should be also AJDT project? I know, that
>>> I don't need "around", only "before" and "after".
>>
>> Nope, project (p2) doesn't have to be an AJDT project if it simply
>> refers to classes from p1 - provided you aren't expecting the aspects
>> from project (p1) to affect project (p2).
>
> When (p2) is just Java project I have following error:
>
> Severity Description Resource In Folder Location Creation
> Time Id
> 2 The project cannot be built until its prerequisite ru.nlmk.lab.core
> is built. Cleaning and building all projects is recommended
> ru.nlmk.lab.admin.ui January 11, 2006 9:00:35 AM 926
>
Ah yes, I suspect this is related to the fact that the 'state' object
for the AJDT project isn't compatible with the JDT project dependency
analysis logic so it can't verify the previous build of the AJDT project
was successful (another thing we have had on our TODO list for a while).
> No matter, how much I do clear and rebuild, I still have this error.
>
> I saw in google also same error for ANT building where was comment,
> that _all_ projects referencing on ANT builded projects should be also
> ANT builded. So, it seems that with AJDT I have same problem.
You might be able to get around this by changing the kind of dependency
amongst the projects. If you change it to a class folder dependency
that might help (that's what I'd do if it was a 'project' dependency but
as you are working with plugins, I don't know how easy it is for you to
do this).
>>> 3. Damn, in p1 I have _one_ aspect and _two_ beans that should be
>>> processed. And right now it takes almost _6_ seconds to compile such
>>> trivial case?! I use 256 Mb for Eclipse, so I think that memory is
>>> not problem.
>>
>> Personally, I run -Xmx768M for eclipse. In the case you describe, (1
>> aspect, 2 beans) you should see sub-second compiles. As an
>> experiment, can you try it with more memory, 512M?
>
> With separate workspace and 512M situation is a little better, but
> still slow.
>
> 9:06:26 AM
> ============================================================ ===============================
>
> 9:06:26 AM Build kind = AUTOBUILD
> 9:06:26 AM Project=ru.nlmk.lab.core kind of build requested
> =Incremental AspectJ compilation
> 9:06:26 AM build: Examined delta - source file changes in required
> project ru.nlmk.lab.core
> 9:06:27 AM Timer event: 1102ms: Time to first compiled message
> 9:06:27 AM Timer event: 1192ms: Time to first woven message
> 9:06:27 AM AspectJ reports build successful, build was: INCREMENTAL
> 9:06:27 AM Timer event: 1242ms: Total time spent in AJDE
> 9:06:28 AM Timer event: 30ms: Create element map (34 rels in
> project: ru.nlmk.lab.core)
> 9:06:28 AM Types affected during build = 1
> 9:06:28 AM Timer event: 0ms: Add markers (11 markers)
> 9:06:28 AM Timer event: 1612ms: Total time spent in AJBuilder.build()
>
I've not done *any* performance analysis of 1.5.0 - 1.5.0 was all about
Java5 and it is possible there have been some regressions that we need
to sort out. I will take a look, for a project as small as you say, I'd
suspect it to run at least twice as fast as you are showing.
Andy.
|
|
|
| Re: AJDT is slow [message #60466 is a reply to message #60446] |
Wed, 11 January 2006 11:28 |
| Eclipse User |
|
|
|
Originally posted by: scheglov_ke.nlmk.ru
Andy Clement wrote:
>> When (p2) is just Java project I have following error:
>>
>> Severity Description Resource In Folder Location
>> Creation Time Id
>> 2 The project cannot be built until its prerequisite
>> ru.nlmk.lab.core is built. Cleaning and building all projects is
>> recommended ru.nlmk.lab.admin.ui January 11, 2006 9:00:35
>> AM 926
>>
> Ah yes, I suspect this is related to the fact that the 'state' object
> for the AJDT project isn't compatible with the JDT project dependency
> analysis logic so it can't verify the previous build of the AJDT project
> was successful (another thing we have had on our TODO list for a while).
>
>> No matter, how much I do clear and rebuild, I still have this error.
>>
>> I saw in google also same error for ANT building where was comment,
>> that _all_ projects referencing on ANT builded projects should be also
>> ANT builded. So, it seems that with AJDT I have same problem.
>
>
> You might be able to get around this by changing the kind of dependency
> amongst the projects. If you change it to a class folder dependency
> that might help (that's what I'd do if it was a 'project' dependency but
> as you are working with plugins, I don't know how easy it is for you to
> do this).
Ok, so I know that this problem is known and I will wait for
solution. :-)
This would be not so much problem, if AJDT compiler would be fast
enough...
>> 9:06:28 AM Timer event: 0ms: Add markers (11 markers)
>> 9:06:28 AM Timer event: 1612ms: Total time spent in AJBuilder.build()
>>
> I've not done *any* performance analysis of 1.5.0 - 1.5.0 was all about
> Java5 and it is possible there have been some regressions that we need
> to sort out. I will take a look, for a project as small as you say, I'd
> suspect it to run at least twice as fast as you are showing.
Ok, thank you.
I am not sure why you say "twice". Just for information: I use
P4-1300 with 768 Mb memory. WinXP, Java 1.5 and Eclipse 3.1.1.
--
SY, Konstantin.
Advanced Eclipse SWT Designer (http://www.swt-designer.com)
|
|
|
| Re: AJDT is slow [message #60487 is a reply to message #60466] |
Wed, 11 January 2006 11:46 |
| Eclipse User |
|
|
|
Originally posted by: clemas.uk.ibm.com
Konstantin Scheglov wrote:
>> I've not done *any* performance analysis of 1.5.0 - 1.5.0 was all
>> about Java5 and it is possible there have been some regressions that
>> we need to sort out. I will take a look, for a project as small as
>> you say, I'd suspect it to run at least twice as fast as you are showing.
>
> Ok, thank you.
>
> I am not sure why you say "twice". Just for information: I use P4-1300
> with 768 Mb memory. WinXP, Java 1.5 and Eclipse 3.1.1.
>
Twice was just a word I plucked out of the air as being what I think the
absolute worst case should be (~ half a second) - in fact with the
testing I did this morning, it's working better than I expected. I
tried to replicate your project, 2 classes ('beans') and a simple aspect
doing a heavy within(*) pointcut and some ITDs. If I change some of the
files and save:
09:41:26 Build kind = AUTOBUILD
09:41:26 Project=PerfAnalysis kind of build requested
=Incremental AspectJ compilation
09:41:26 build: Examined delta - source file changes in required
project PerfAnalysis
09:41:26 Timer event: 140ms: Time to first compiled message
09:41:26 Timer event: 150ms: Time to first woven message
09:41:26 AspectJ reports build successful, build was: INCREMENTAL
09:41:26 Timer event: 200ms: Total time spent in AJDE
09:41:26 Timer event: 10ms: Create element map (30 rels in project:
PerfAnalysis)
09:41:26 Types affected during build = 3
09:41:26 Timer event: 0ms: Add markers (11 markers)
09:41:26 Timer event: 271ms: Total time spent in AJBuilder.build()
09:41:58 Build kind = AUTOBUILD
09:41:58 Project=PerfAnalysis kind of build requested
=Incremental AspectJ compilation
09:41:58 build: Examined delta - source file changes in required
project PerfAnalysis
09:41:58 Timer event: 131ms: Time to first compiled message
09:41:58 Timer event: 161ms: Time to first woven message
09:41:58 AspectJ reports build successful, build was: INCREMENTAL
09:41:58 Timer event: 301ms: Total time spent in AJDE
09:41:58 Timer event: 0ms: Create element map (30 rels in project:
PerfAnalysis)
09:41:58 Types affected during build = 3
09:41:58 Timer event: 0ms: Add markers (11 markers)
09:41:58 Timer event: 411ms: Total time spent in AJBuilder.build()
admittedly my beans were simple and my laptop is fast (PentiumM 2Ghz,
2Gig RAM). I also don't have multiple AspectJ projects, just that one.
Andy.
|
|
|
| Re: AJDT is slow [message #591677 is a reply to message #60353] |
Tue, 10 January 2006 12:50 |
 Andrew Clement
Messages: 162
Registered: July 2009 |
Senior Member |
|
|
Konstantin Scheglov wrote:
>
> I have several performance related questions.
>
> 1. What is AJDE and why is it so slow? See log log from "AJDT Event
> Trace" below.
AJDE is the AspectJ compiler itself which is called by the AJDT builder.
It is slower than a regular java compile because of the necessary
pointcut matching and weaving that has to occur for aspects.
*However* if you modify a single java class and save it, the subsequent
incremental compilation should take no more than 1 second.
>
> 2. Is it true, that if I have one project (p1) with aspects (and classes
> that should be processed) and other project (p2) that _uses_ processed
> classes, then p2 should be also AJDT project? I know, that I don't need
> "around", only "before" and "after".
Nope, project (p2) doesn't have to be an AJDT project if it simply
refers to classes from p1 - provided you aren't expecting the aspects
from project (p1) to affect project (p2).
>
> 3. Damn, in p1 I have _one_ aspect and _two_ beans that should be
> processed. And right now it takes almost _6_ seconds to compile such
> trivial case?! I use 256 Mb for Eclipse, so I think that memory is not
> problem.
Personally, I run -Xmx768M for eclipse. In the case you describe, (1
aspect, 2 beans) you should see sub-second compiles. As an experiment,
can you try it with more memory, 512M?
Andy.
|
|
|
| Re: AJDT is slow [message #591698 is a reply to message #60377] |
Wed, 11 January 2006 06:22 |
Konstantin Scheglov
Messages: 555
Registered: July 2009 |
Senior Member |
|
|
Andy Clement wrote:
>> I have several performance related questions.
>>
>> 1. What is AJDE and why is it so slow? See log log from "AJDT Event
>> Trace" below.
>
>
> AJDE is the AspectJ compiler itself which is called by the AJDT builder.
> It is slower than a regular java compile because of the necessary
> pointcut matching and weaving that has to occur for aspects.
>
> *However* if you modify a single java class and save it, the subsequent
> incremental compilation should take no more than 1 second.
Now I've changed to use separate workspace with only my current
projects (plugins, because I work on RCP). I am only in beginning, so
these projects are small:
1. ru.nlmk.libraries.external - with pile of jar's;
2. ru.nlmk.lab.core - core plugin with beans and aspect;
3. ru.nlmk.lab.admin.ui - currently only UI plugin that uses core;
4. ru.nlmk.lab.admin.application - application for RCP;
5. org.eclipse.jface.databinding - source snapshot of data binding
project (for fixing bug that present in 3.2M4).
Note, that I use Eclipse 3.1.1 (only bindings from 3.2M4).
JDT works very fast, I can see only short flashing of progress in
bottom right corner.
>> 2. Is it true, that if I have one project (p1) with aspects (and
>> classes that should be processed) and other project (p2) that _uses_
>> processed classes, then p2 should be also AJDT project? I know, that I
>> don't need "around", only "before" and "after".
>
>
> Nope, project (p2) doesn't have to be an AJDT project if it simply
> refers to classes from p1 - provided you aren't expecting the aspects
> from project (p1) to affect project (p2).
When (p2) is just Java project I have following error:
Severity Description Resource In Folder Location Creation Time Id
2 The project cannot be built until its prerequisite ru.nlmk.lab.core is
built. Cleaning and building all projects is recommended
ru.nlmk.lab.admin.ui January 11, 2006 9:00:35 AM 926
No matter, how much I do clear and rebuild, I still have this error.
I saw in google also same error for ANT building where was comment,
that _all_ projects referencing on ANT builded projects should be also
ANT builded. So, it seems that with AJDT I have same problem.
>> 3. Damn, in p1 I have _one_ aspect and _two_ beans that should be
>> processed. And right now it takes almost _6_ seconds to compile such
>> trivial case?! I use 256 Mb for Eclipse, so I think that memory is not
>> problem.
>
>
> Personally, I run -Xmx768M for eclipse. In the case you describe, (1
> aspect, 2 beans) you should see sub-second compiles. As an experiment,
> can you try it with more memory, 512M?
With separate workspace and 512M situation is a little better, but
still slow.
9:06:26 AM
============================================================ ===============================
9:06:26 AM Build kind = AUTOBUILD
9:06:26 AM Project=ru.nlmk.lab.core kind of build requested
=Incremental AspectJ compilation
9:06:26 AM build: Examined delta - source file changes in required
project ru.nlmk.lab.core
9:06:27 AM Timer event: 1102ms: Time to first compiled message
9:06:27 AM Timer event: 1192ms: Time to first woven message
9:06:27 AM AspectJ reports build successful, build was: INCREMENTAL
9:06:27 AM Timer event: 1242ms: Total time spent in AJDE
9:06:28 AM Timer event: 30ms: Create element map (34 rels in project:
ru.nlmk.lab.core)
9:06:28 AM Types affected during build = 1
9:06:28 AM Timer event: 0ms: Add markers (11 markers)
9:06:28 AM Timer event: 1612ms: Total time spent in AJBuilder.build()
--
SY, Konstantin.
Advanced Eclipse SWT Designer (http://www.swt-designer.com)
Konstantin Scheglov,
Google, Inc.
|
|
|
| Re: AJDT is slow [message #591709 is a reply to message #60423] |
Wed, 11 January 2006 09:15 |
Andrew Clement
Messages: 162
Registered: July 2009 |
Senior Member |
|
|
Konstantin Scheglov wrote:
>>> 2. Is it true, that if I have one project (p1) with aspects (and
>>> classes that should be processed) and other project (p2) that _uses_
>>> processed classes, then p2 should be also AJDT project? I know, that
>>> I don't need "around", only "before" and "after".
>>
>> Nope, project (p2) doesn't have to be an AJDT project if it simply
>> refers to classes from p1 - provided you aren't expecting the aspects
>> from project (p1) to affect project (p2).
>
> When (p2) is just Java project I have following error:
>
> Severity Description Resource In Folder Location Creation
> Time Id
> 2 The project cannot be built until its prerequisite ru.nlmk.lab.core
> is built. Cleaning and building all projects is recommended
> ru.nlmk.lab.admin.ui January 11, 2006 9:00:35 AM 926
>
Ah yes, I suspect this is related to the fact that the 'state' object
for the AJDT project isn't compatible with the JDT project dependency
analysis logic so it can't verify the previous build of the AJDT project
was successful (another thing we have had on our TODO list for a while).
> No matter, how much I do clear and rebuild, I still have this error.
>
> I saw in google also same error for ANT building where was comment,
> that _all_ projects referencing on ANT builded projects should be also
> ANT builded. So, it seems that with AJDT I have same problem.
You might be able to get around this by changing the kind of dependency
amongst the projects. If you change it to a class folder dependency
that might help (that's what I'd do if it was a 'project' dependency but
as you are working with plugins, I don't know how easy it is for you to
do this).
>>> 3. Damn, in p1 I have _one_ aspect and _two_ beans that should be
>>> processed. And right now it takes almost _6_ seconds to compile such
>>> trivial case?! I use 256 Mb for Eclipse, so I think that memory is
>>> not problem.
>>
>> Personally, I run -Xmx768M for eclipse. In the case you describe, (1
>> aspect, 2 beans) you should see sub-second compiles. As an
>> experiment, can you try it with more memory, 512M?
>
> With separate workspace and 512M situation is a little better, but
> still slow.
>
> 9:06:26 AM
> ============================================================ ===============================
>
> 9:06:26 AM Build kind = AUTOBUILD
> 9:06:26 AM Project=ru.nlmk.lab.core kind of build requested
> =Incremental AspectJ compilation
> 9:06:26 AM build: Examined delta - source file changes in required
> project ru.nlmk.lab.core
> 9:06:27 AM Timer event: 1102ms: Time to first compiled message
> 9:06:27 AM Timer event: 1192ms: Time to first woven message
> 9:06:27 AM AspectJ reports build successful, build was: INCREMENTAL
> 9:06:27 AM Timer event: 1242ms: Total time spent in AJDE
> 9:06:28 AM Timer event: 30ms: Create element map (34 rels in
> project: ru.nlmk.lab.core)
> 9:06:28 AM Types affected during build = 1
> 9:06:28 AM Timer event: 0ms: Add markers (11 markers)
> 9:06:28 AM Timer event: 1612ms: Total time spent in AJBuilder.build()
>
I've not done *any* performance analysis of 1.5.0 - 1.5.0 was all about
Java5 and it is possible there have been some regressions that we need
to sort out. I will take a look, for a project as small as you say, I'd
suspect it to run at least twice as fast as you are showing.
Andy.
|
|
|
| Re: AJDT is slow [message #591718 is a reply to message #60446] |
Wed, 11 January 2006 11:28 |
Konstantin Scheglov
Messages: 555
Registered: July 2009 |
Senior Member |
|
|
Andy Clement wrote:
>> When (p2) is just Java project I have following error:
>>
>> Severity Description Resource In Folder Location
>> Creation Time Id
>> 2 The project cannot be built until its prerequisite
>> ru.nlmk.lab.core is built. Cleaning and building all projects is
>> recommended ru.nlmk.lab.admin.ui January 11, 2006 9:00:35
>> AM 926
>>
> Ah yes, I suspect this is related to the fact that the 'state' object
> for the AJDT project isn't compatible with the JDT project dependency
> analysis logic so it can't verify the previous build of the AJDT project
> was successful (another thing we have had on our TODO list for a while).
>
>> No matter, how much I do clear and rebuild, I still have this error.
>>
>> I saw in google also same error for ANT building where was comment,
>> that _all_ projects referencing on ANT builded projects should be also
>> ANT builded. So, it seems that with AJDT I have same problem.
>
>
> You might be able to get around this by changing the kind of dependency
> amongst the projects. If you change it to a class folder dependency
> that might help (that's what I'd do if it was a 'project' dependency but
> as you are working with plugins, I don't know how easy it is for you to
> do this).
Ok, so I know that this problem is known and I will wait for
solution. :-)
This would be not so much problem, if AJDT compiler would be fast
enough...
>> 9:06:28 AM Timer event: 0ms: Add markers (11 markers)
>> 9:06:28 AM Timer event: 1612ms: Total time spent in AJBuilder.build()
>>
> I've not done *any* performance analysis of 1.5.0 - 1.5.0 was all about
> Java5 and it is possible there have been some regressions that we need
> to sort out. I will take a look, for a project as small as you say, I'd
> suspect it to run at least twice as fast as you are showing.
Ok, thank you.
I am not sure why you say "twice". Just for information: I use
P4-1300 with 768 Mb memory. WinXP, Java 1.5 and Eclipse 3.1.1.
--
SY, Konstantin.
Advanced Eclipse SWT Designer (http://www.swt-designer.com)
Konstantin Scheglov,
Google, Inc.
|
|
|
| Re: AJDT is slow [message #591730 is a reply to message #60466] |
Wed, 11 January 2006 11:46 |
Andrew Clement
Messages: 162
Registered: July 2009 |
Senior Member |
|
|
Konstantin Scheglov wrote:
>> I've not done *any* performance analysis of 1.5.0 - 1.5.0 was all
>> about Java5 and it is possible there have been some regressions that
>> we need to sort out. I will take a look, for a project as small as
>> you say, I'd suspect it to run at least twice as fast as you are showing.
>
> Ok, thank you.
>
> I am not sure why you say "twice". Just for information: I use P4-1300
> with 768 Mb memory. WinXP, Java 1.5 and Eclipse 3.1.1.
>
Twice was just a word I plucked out of the air as being what I think the
absolute worst case should be (~ half a second) - in fact with the
testing I did this morning, it's working better than I expected. I
tried to replicate your project, 2 classes ('beans') and a simple aspect
doing a heavy within(*) pointcut and some ITDs. If I change some of the
files and save:
09:41:26 Build kind = AUTOBUILD
09:41:26 Project=PerfAnalysis kind of build requested
=Incremental AspectJ compilation
09:41:26 build: Examined delta - source file changes in required
project PerfAnalysis
09:41:26 Timer event: 140ms: Time to first compiled message
09:41:26 Timer event: 150ms: Time to first woven message
09:41:26 AspectJ reports build successful, build was: INCREMENTAL
09:41:26 Timer event: 200ms: Total time spent in AJDE
09:41:26 Timer event: 10ms: Create element map (30 rels in project:
PerfAnalysis)
09:41:26 Types affected during build = 3
09:41:26 Timer event: 0ms: Add markers (11 markers)
09:41:26 Timer event: 271ms: Total time spent in AJBuilder.build()
09:41:58 Build kind = AUTOBUILD
09:41:58 Project=PerfAnalysis kind of build requested
=Incremental AspectJ compilation
09:41:58 build: Examined delta - source file changes in required
project PerfAnalysis
09:41:58 Timer event: 131ms: Time to first compiled message
09:41:58 Timer event: 161ms: Time to first woven message
09:41:58 AspectJ reports build successful, build was: INCREMENTAL
09:41:58 Timer event: 301ms: Total time spent in AJDE
09:41:58 Timer event: 0ms: Create element map (30 rels in project:
PerfAnalysis)
09:41:58 Types affected during build = 3
09:41:58 Timer event: 0ms: Add markers (11 markers)
09:41:58 Timer event: 411ms: Total time spent in AJBuilder.build()
admittedly my beans were simple and my laptop is fast (PentiumM 2Ghz,
2Gig RAM). I also don't have multiple AspectJ projects, just that one.
Andy.
|
|
|
Goto Forum:
Current Time: Thu Apr 25 08:15:33 GMT 2024
Powered by FUDForum. Page generated in 0.04126 seconds |
] 
Search
Help
Register
Login
Home
