Home » Language IDEs » AspectJ » Memory requirement for ajdt
|
| Re: Memory requirement for ajdt [message #46720 is a reply to message #46699] |
Sun, 23 January 2005 22:57   |
Eclipse User |
|
|
|
Originally posted by: mchapman.uk.ibm.com
Hi Harry,
What do you consider to be a "small" project? Could you provide a count of
the number of lines of code to give a better means of comparison?
AJDT itself consists of a number of AspectJ projects, with around
50,000 lines of code, plus a couple of Java projects. We tend to run with
-Xmx256m, and never get out of memory errors. Is your project larger than
this?
You say the memory usage goes up to 500MB if you compile only the AspectJ
project, but then when you do a build all, the usage doesn't go over
100MB, although it then doesn't work - in what way does it fail? Are you
sure Eclipse is picking up your -vmargs -Xmx512m option?
Regards,
Matt.
On Sun, 23 Jan 2005 02:28:04 +0000, Harry Sheng wrote:
> Hi,
>
> I am wondering how many MB memory would be appropriate for a relatively
> small project to use AJDT.
>
> My environment is P4 2.6G, Win2K, 512M memory. I start eclipse with
> "-Xmx512M". I have one AspectJ project and a couple other java projects.
>
> If I close the AspectJ project, I do not have problem to do build-all to
> all the java projects.
>
> If I only compile the AspectJ project, the memory usage goes up to 500MB,
> and I almost get one out-of-memory error for every 3 compiles. (Only
> Eclipse, no other applications)
>
> I have never succeeded to do a build-all with AspectJ project and all
> other java projects open. (The peak memory usage from Win2K taskmanager
> shows only 100MB).
>
>
>
> Harry Sheng
|
|
|
| Re: Memory requirement for ajdt [message #46783 is a reply to message #46720] |
Mon, 24 January 2005 16:25 |
 harry sheng
Messages: 37
Registered: July 2009 |
Member |
|
|
Since my code already compiled, I did the following to check your comments:
1. Close all java projects and only keep the AspectJ project open in the
AJDT.
2. Close and then re-open Eclipse
3. Manually delete the build directory of the AspectJ project.
4. Click the "project->clean..." to do a clean build of the AspectJ project
I repeated step 3 and 4 for 6 times, and get the following data from the
Win2K task manager:
Mem Usage Peak Mem Usage VM Size
61M 61M 60M (Right after re-open Eclipse)
193M 194M 190M (After 1st clean-build)
218M 219M 278M (After 2nd clean-build)
239M 240M 282M (After 3rd clean-build)
285M 288M 283M (After 4th clean-build)
289M 289M 287M (After 5th clean-build)
291M 292M 289M (After 6th clean-build)
Looks like the memory usage has an increase trend.
I guess the "out of memory" problem I had is related to this memory usage
trend? What I normally do is saving the change I made to a class or advice
before I go to the next one. This saving would trigger a auto-build of the
project and increase the memory locked by the project.
After a couple of "out of memory" crash, I clicked the "save" button more
often, which may make the situation even worse?
Close the AspectJ project, the memory foot-print in the Win2k task manager
shrink back to 60M.
Did a similiar "clean-build-all" test to my all other 7 java projects. The
memory usage foot-print was better. Relatively stable.
Matt Chapman wrote:
> Hi Harry,
> What do you consider to be a "small" project? Could you provide a count of
> the number of lines of code to give a better means of comparison?
> AJDT itself consists of a number of AspectJ projects, with around
> 50,000 lines of code, plus a couple of Java projects. We tend to run with
> -Xmx256m, and never get out of memory errors. Is your project larger than
> this?
One "around()" advice and one "before(): handler()" advice on about 120
classes with about 50,000 lines of code. And a couple of other advices
that only affect a limited number of classes.
My project have a total of about 100,000 lines of code.
> You say the memory usage goes up to 500MB if you compile only the AspectJ
> project, but then when you do a build all, the usage doesn't go over
> 100MB, although it then doesn't work - in what way does it fail? Are you
> sure Eclipse is picking up your -vmargs -Xmx512m option?
> Regards,
> Matt.
> On Sun, 23 Jan 2005 02:28:04 +0000, Harry Sheng wrote:
>> Hi,
>>
>> I am wondering how many MB memory would be appropriate for a relatively
>> small project to use AJDT.
>>
>> My environment is P4 2.6G, Win2K, 512M memory. I start eclipse with
>> "-Xmx512M". I have one AspectJ project and a couple other java projects.
>>
>> If I close the AspectJ project, I do not have problem to do build-all to
>> all the java projects.
>>
>> If I only compile the AspectJ project, the memory usage goes up to 500MB,
>> and I almost get one out-of-memory error for every 3 compiles. (Only
>> Eclipse, no other applications)
>>
>> I have never succeeded to do a build-all with AspectJ project and all
>> other java projects open. (The peak memory usage from Win2K taskmanager
>> shows only 100MB).
>>
>>
>>
>> Harry Sheng
|
|
|
| Re: Memory requirement for ajdt [message #46813 is a reply to message #46720] |
Mon, 24 January 2005 16:25 |
harry sheng
Messages: 37
Registered: July 2009 |
Member |
|
|
Since my code already compiled, I did the following to check your comments:
1. Close all java projects and only keep the AspectJ project open in the
AJDT.
2. Close and then re-open Eclipse
3. Manually delete the build directory of the AspectJ project.
4. Click the "project->clean..." to do a clean build of the AspectJ project
I repeated step 3 and 4 for 6 times, and get the following data from the
Win2K task manager:
Mem Usage Peak Mem Usage VM Size
61M 61M 60M (Right after re-open Eclipse)
193M 194M 190M (After 1st clean-build)
218M 219M 278M (After 2nd clean-build)
239M 240M 282M (After 3rd clean-build)
285M 288M 283M (After 4th clean-build)
289M 289M 287M (After 5th clean-build)
291M 292M 289M (After 6th clean-build)
Looks like the memory usage has an increase trend.
I guess the "out of memory" problem I had is related to this memory usage
trend? What I normally do is saving the change I made to a class or advice
before I go to the next one. This saving would trigger a auto-build of the
project and increase the memory locked by the project.
After a couple of "out of memory" crash, I clicked the "save" button more
often, which may make the situation even worse?
Close the AspectJ project, the memory foot-print in the Win2k task manager
shrink back to 60M.
Did a similiar "clean-build-all" test to my all other 7 java projects. The
memory usage foot-print was better. Relatively stable.
Matt Chapman wrote:
> Hi Harry,
> What do you consider to be a "small" project? Could you provide a count of
> the number of lines of code to give a better means of comparison?
> AJDT itself consists of a number of AspectJ projects, with around
> 50,000 lines of code, plus a couple of Java projects. We tend to run with
> -Xmx256m, and never get out of memory errors. Is your project larger than
> this?
One "around()" advice and one "before(): handler()" advice on about 120
classes with about 50,000 lines of code. And a couple of other advices
that only affect a limited number of classes.
My project have a total of about 100,000 lines of code.
> You say the memory usage goes up to 500MB if you compile only the AspectJ
> project, but then when you do a build all, the usage doesn't go over
> 100MB, although it then doesn't work - in what way does it fail? Are you
> sure Eclipse is picking up your -vmargs -Xmx512m option?
> Regards,
> Matt.
> On Sun, 23 Jan 2005 02:28:04 +0000, Harry Sheng wrote:
>> Hi,
>>
>> I am wondering how many MB memory would be appropriate for a relatively
>> small project to use AJDT.
>>
>> My environment is P4 2.6G, Win2K, 512M memory. I start eclipse with
>> "-Xmx512M". I have one AspectJ project and a couple other java projects.
>>
>> If I close the AspectJ project, I do not have problem to do build-all to
>> all the java projects.
>>
>> If I only compile the AspectJ project, the memory usage goes up to 500MB,
>> and I almost get one out-of-memory error for every 3 compiles. (Only
>> Eclipse, no other applications)
>>
>> I have never succeeded to do a build-all with AspectJ project and all
>> other java projects open. (The peak memory usage from Win2K taskmanager
>> shows only 100MB).
>>
>>
>>
>> Harry Sheng
|
|
|
| Re: Memory requirement for ajdt [message #46902 is a reply to message #46783] |
Mon, 24 January 2005 17:29 |
| Eclipse User |
|
|
|
Originally posted by: mchapman.uk.ibm.com
It does indeed look like a memory leak bug. Which version of AJDT are you
using? If it's not AJDT 1.2.0M2, please could you try that first, and then
raise a bug if you still get the problem.
Thanks,
Matt.
On Mon, 24 Jan 2005 16:25:45 +0000, harry sheng wrote:
> Since my code already compiled, I did the following to check your comments:
>
> 1. Close all java projects and only keep the AspectJ project open in the
> AJDT.
> 2. Close and then re-open Eclipse
> 3. Manually delete the build directory of the AspectJ project.
> 4. Click the "project->clean..." to do a clean build of the AspectJ project
>
> I repeated step 3 and 4 for 6 times, and get the following data from the
> Win2K task manager:
>
> Mem Usage Peak Mem Usage VM Size
> 61M 61M 60M (Right after re-open Eclipse)
> 193M 194M 190M (After 1st clean-build)
> 218M 219M 278M (After 2nd clean-build)
> 239M 240M 282M (After 3rd clean-build)
> 285M 288M 283M (After 4th clean-build)
> 289M 289M 287M (After 5th clean-build)
> 291M 292M 289M (After 6th clean-build)
>
> Looks like the memory usage has an increase trend.
>
> I guess the "out of memory" problem I had is related to this memory usage
> trend? What I normally do is saving the change I made to a class or advice
> before I go to the next one. This saving would trigger a auto-build of the
> project and increase the memory locked by the project.
>
> After a couple of "out of memory" crash, I clicked the "save" button more
> often, which may make the situation even worse?
>
> Close the AspectJ project, the memory foot-print in the Win2k task manager
> shrink back to 60M.
>
> Did a similiar "clean-build-all" test to my all other 7 java projects. The
> memory usage foot-print was better. Relatively stable.
|
|
|
| Re: Memory requirement for ajdt [message #46958 is a reply to message #46902] |
Mon, 24 January 2005 18:20 |
harry sheng
Messages: 37
Registered: July 2009 |
Member |
|
|
Eclipse AspectJ Development Tools
Version: 1.2.0
Build id: 20041214165937
AspectJ version: 1.5.0M1
(c) Copyright IBM Corp. and others 2000, 2004. All rights reserved.
Visit http://www.eclipse.org/ajdt
Looks like I was using AJDT 1.2.0M2.
I will raise a bug report.
Matt Chapman wrote:
> It does indeed look like a memory leak bug. Which version of AJDT are you
> using? If it's not AJDT 1.2.0M2, please could you try that first, and then
> raise a bug if you still get the problem.
> Thanks,
> Matt.
> On Mon, 24 Jan 2005 16:25:45 +0000, harry sheng wrote:
>> Since my code already compiled, I did the following to check your comments:
>>
>> 1. Close all java projects and only keep the AspectJ project open in the
>> AJDT.
>> 2. Close and then re-open Eclipse
>> 3. Manually delete the build directory of the AspectJ project.
>> 4. Click the "project->clean..." to do a clean build of the AspectJ project
>>
>> I repeated step 3 and 4 for 6 times, and get the following data from the
>> Win2K task manager:
>>
>> Mem Usage Peak Mem Usage VM Size
>> 61M 61M 60M (Right after re-open Eclipse)
>> 193M 194M 190M (After 1st clean-build)
>> 218M 219M 278M (After 2nd clean-build)
>> 239M 240M 282M (After 3rd clean-build)
>> 285M 288M 283M (After 4th clean-build)
>> 289M 289M 287M (After 5th clean-build)
>> 291M 292M 289M (After 6th clean-build)
>>
>> Looks like the memory usage has an increase trend.
>>
>> I guess the "out of memory" problem I had is related to this memory usage
>> trend? What I normally do is saving the change I made to a class or advice
>> before I go to the next one. This saving would trigger a auto-build of the
>> project and increase the memory locked by the project.
>>
>> After a couple of "out of memory" crash, I clicked the "save" button more
>> often, which may make the situation even worse?
>>
>> Close the AspectJ project, the memory foot-print in the Win2k task manager
>> shrink back to 60M.
>>
>> Did a similiar "clean-build-all" test to my all other 7 java projects. The
>> memory usage foot-print was better. Relatively stable.
|
|
|
| Re: Memory requirement for ajdt [message #586109 is a reply to message #46699] |
Sun, 23 January 2005 22:57 |
Matt Chapman
Messages: 429
Registered: July 2009 |
Senior Member |
|
|
Hi Harry,
What do you consider to be a "small" project? Could you provide a count of
the number of lines of code to give a better means of comparison?
AJDT itself consists of a number of AspectJ projects, with around
50,000 lines of code, plus a couple of Java projects. We tend to run with
-Xmx256m, and never get out of memory errors. Is your project larger than
this?
You say the memory usage goes up to 500MB if you compile only the AspectJ
project, but then when you do a build all, the usage doesn't go over
100MB, although it then doesn't work - in what way does it fail? Are you
sure Eclipse is picking up your -vmargs -Xmx512m option?
Regards,
Matt.
On Sun, 23 Jan 2005 02:28:04 +0000, Harry Sheng wrote:
> Hi,
>
> I am wondering how many MB memory would be appropriate for a relatively
> small project to use AJDT.
>
> My environment is P4 2.6G, Win2K, 512M memory. I start eclipse with
> "-Xmx512M". I have one AspectJ project and a couple other java projects.
>
> If I close the AspectJ project, I do not have problem to do build-all to
> all the java projects.
>
> If I only compile the AspectJ project, the memory usage goes up to 500MB,
> and I almost get one out-of-memory error for every 3 compiles. (Only
> Eclipse, no other applications)
>
> I have never succeeded to do a build-all with AspectJ project and all
> other java projects open. (The peak memory usage from Win2K taskmanager
> shows only 100MB).
>
>
>
> Harry Sheng
|
|
|
| Re: Memory requirement for ajdt [message #586159 is a reply to message #46720] |
Mon, 24 January 2005 16:25 |
harry sheng
Messages: 37
Registered: July 2009 |
Member |
|
|
Since my code already compiled, I did the following to check your comments:
1. Close all java projects and only keep the AspectJ project open in the
AJDT.
2. Close and then re-open Eclipse
3. Manually delete the build directory of the AspectJ project.
4. Click the "project->clean..." to do a clean build of the AspectJ project
I repeated step 3 and 4 for 6 times, and get the following data from the
Win2K task manager:
Mem Usage Peak Mem Usage VM Size
61M 61M 60M (Right after re-open Eclipse)
193M 194M 190M (After 1st clean-build)
218M 219M 278M (After 2nd clean-build)
239M 240M 282M (After 3rd clean-build)
285M 288M 283M (After 4th clean-build)
289M 289M 287M (After 5th clean-build)
291M 292M 289M (After 6th clean-build)
Looks like the memory usage has an increase trend.
I guess the "out of memory" problem I had is related to this memory usage
trend? What I normally do is saving the change I made to a class or advice
before I go to the next one. This saving would trigger a auto-build of the
project and increase the memory locked by the project.
After a couple of "out of memory" crash, I clicked the "save" button more
often, which may make the situation even worse?
Close the AspectJ project, the memory foot-print in the Win2k task manager
shrink back to 60M.
Did a similiar "clean-build-all" test to my all other 7 java projects. The
memory usage foot-print was better. Relatively stable.
Matt Chapman wrote:
> Hi Harry,
> What do you consider to be a "small" project? Could you provide a count of
> the number of lines of code to give a better means of comparison?
> AJDT itself consists of a number of AspectJ projects, with around
> 50,000 lines of code, plus a couple of Java projects. We tend to run with
> -Xmx256m, and never get out of memory errors. Is your project larger than
> this?
One "around()" advice and one "before(): handler()" advice on about 120
classes with about 50,000 lines of code. And a couple of other advices
that only affect a limited number of classes.
My project have a total of about 100,000 lines of code.
> You say the memory usage goes up to 500MB if you compile only the AspectJ
> project, but then when you do a build all, the usage doesn't go over
> 100MB, although it then doesn't work - in what way does it fail? Are you
> sure Eclipse is picking up your -vmargs -Xmx512m option?
> Regards,
> Matt.
> On Sun, 23 Jan 2005 02:28:04 +0000, Harry Sheng wrote:
>> Hi,
>>
>> I am wondering how many MB memory would be appropriate for a relatively
>> small project to use AJDT.
>>
>> My environment is P4 2.6G, Win2K, 512M memory. I start eclipse with
>> "-Xmx512M". I have one AspectJ project and a couple other java projects.
>>
>> If I close the AspectJ project, I do not have problem to do build-all to
>> all the java projects.
>>
>> If I only compile the AspectJ project, the memory usage goes up to 500MB,
>> and I almost get one out-of-memory error for every 3 compiles. (Only
>> Eclipse, no other applications)
>>
>> I have never succeeded to do a build-all with AspectJ project and all
>> other java projects open. (The peak memory usage from Win2K taskmanager
>> shows only 100MB).
>>
>>
>>
>> Harry Sheng
|
|
|
| Re: Memory requirement for ajdt [message #586167 is a reply to message #46720] |
Mon, 24 January 2005 16:25 |
harry sheng
Messages: 37
Registered: July 2009 |
Member |
|
|
Since my code already compiled, I did the following to check your comments:
1. Close all java projects and only keep the AspectJ project open in the
AJDT.
2. Close and then re-open Eclipse
3. Manually delete the build directory of the AspectJ project.
4. Click the "project->clean..." to do a clean build of the AspectJ project
I repeated step 3 and 4 for 6 times, and get the following data from the
Win2K task manager:
Mem Usage Peak Mem Usage VM Size
61M 61M 60M (Right after re-open Eclipse)
193M 194M 190M (After 1st clean-build)
218M 219M 278M (After 2nd clean-build)
239M 240M 282M (After 3rd clean-build)
285M 288M 283M (After 4th clean-build)
289M 289M 287M (After 5th clean-build)
291M 292M 289M (After 6th clean-build)
Looks like the memory usage has an increase trend.
I guess the "out of memory" problem I had is related to this memory usage
trend? What I normally do is saving the change I made to a class or advice
before I go to the next one. This saving would trigger a auto-build of the
project and increase the memory locked by the project.
After a couple of "out of memory" crash, I clicked the "save" button more
often, which may make the situation even worse?
Close the AspectJ project, the memory foot-print in the Win2k task manager
shrink back to 60M.
Did a similiar "clean-build-all" test to my all other 7 java projects. The
memory usage foot-print was better. Relatively stable.
Matt Chapman wrote:
> Hi Harry,
> What do you consider to be a "small" project? Could you provide a count of
> the number of lines of code to give a better means of comparison?
> AJDT itself consists of a number of AspectJ projects, with around
> 50,000 lines of code, plus a couple of Java projects. We tend to run with
> -Xmx256m, and never get out of memory errors. Is your project larger than
> this?
One "around()" advice and one "before(): handler()" advice on about 120
classes with about 50,000 lines of code. And a couple of other advices
that only affect a limited number of classes.
My project have a total of about 100,000 lines of code.
> You say the memory usage goes up to 500MB if you compile only the AspectJ
> project, but then when you do a build all, the usage doesn't go over
> 100MB, although it then doesn't work - in what way does it fail? Are you
> sure Eclipse is picking up your -vmargs -Xmx512m option?
> Regards,
> Matt.
> On Sun, 23 Jan 2005 02:28:04 +0000, Harry Sheng wrote:
>> Hi,
>>
>> I am wondering how many MB memory would be appropriate for a relatively
>> small project to use AJDT.
>>
>> My environment is P4 2.6G, Win2K, 512M memory. I start eclipse with
>> "-Xmx512M". I have one AspectJ project and a couple other java projects.
>>
>> If I close the AspectJ project, I do not have problem to do build-all to
>> all the java projects.
>>
>> If I only compile the AspectJ project, the memory usage goes up to 500MB,
>> and I almost get one out-of-memory error for every 3 compiles. (Only
>> Eclipse, no other applications)
>>
>> I have never succeeded to do a build-all with AspectJ project and all
>> other java projects open. (The peak memory usage from Win2K taskmanager
>> shows only 100MB).
>>
>>
>>
>> Harry Sheng
|
|
|
| Re: Memory requirement for ajdt [message #586213 is a reply to message #46783] |
Mon, 24 January 2005 17:29 |
Matt Chapman
Messages: 429
Registered: July 2009 |
Senior Member |
|
|
It does indeed look like a memory leak bug. Which version of AJDT are you
using? If it's not AJDT 1.2.0M2, please could you try that first, and then
raise a bug if you still get the problem.
Thanks,
Matt.
On Mon, 24 Jan 2005 16:25:45 +0000, harry sheng wrote:
> Since my code already compiled, I did the following to check your comments:
>
> 1. Close all java projects and only keep the AspectJ project open in the
> AJDT.
> 2. Close and then re-open Eclipse
> 3. Manually delete the build directory of the AspectJ project.
> 4. Click the "project->clean..." to do a clean build of the AspectJ project
>
> I repeated step 3 and 4 for 6 times, and get the following data from the
> Win2K task manager:
>
> Mem Usage Peak Mem Usage VM Size
> 61M 61M 60M (Right after re-open Eclipse)
> 193M 194M 190M (After 1st clean-build)
> 218M 219M 278M (After 2nd clean-build)
> 239M 240M 282M (After 3rd clean-build)
> 285M 288M 283M (After 4th clean-build)
> 289M 289M 287M (After 5th clean-build)
> 291M 292M 289M (After 6th clean-build)
>
> Looks like the memory usage has an increase trend.
>
> I guess the "out of memory" problem I had is related to this memory usage
> trend? What I normally do is saving the change I made to a class or advice
> before I go to the next one. This saving would trigger a auto-build of the
> project and increase the memory locked by the project.
>
> After a couple of "out of memory" crash, I clicked the "save" button more
> often, which may make the situation even worse?
>
> Close the AspectJ project, the memory foot-print in the Win2k task manager
> shrink back to 60M.
>
> Did a similiar "clean-build-all" test to my all other 7 java projects. The
> memory usage foot-print was better. Relatively stable.
|
|
|
| Re: Memory requirement for ajdt [message #586243 is a reply to message #46902] |
Mon, 24 January 2005 18:20 |
harry sheng
Messages: 37
Registered: July 2009 |
Member |
|
|
Eclipse AspectJ Development Tools
Version: 1.2.0
Build id: 20041214165937
AspectJ version: 1.5.0M1
(c) Copyright IBM Corp. and others 2000, 2004. All rights reserved.
Visit http://www.eclipse.org/ajdt
Looks like I was using AJDT 1.2.0M2.
I will raise a bug report.
Matt Chapman wrote:
> It does indeed look like a memory leak bug. Which version of AJDT are you
> using? If it's not AJDT 1.2.0M2, please could you try that first, and then
> raise a bug if you still get the problem.
> Thanks,
> Matt.
> On Mon, 24 Jan 2005 16:25:45 +0000, harry sheng wrote:
>> Since my code already compiled, I did the following to check your comments:
>>
>> 1. Close all java projects and only keep the AspectJ project open in the
>> AJDT.
>> 2. Close and then re-open Eclipse
>> 3. Manually delete the build directory of the AspectJ project.
>> 4. Click the "project->clean..." to do a clean build of the AspectJ project
>>
>> I repeated step 3 and 4 for 6 times, and get the following data from the
>> Win2K task manager:
>>
>> Mem Usage Peak Mem Usage VM Size
>> 61M 61M 60M (Right after re-open Eclipse)
>> 193M 194M 190M (After 1st clean-build)
>> 218M 219M 278M (After 2nd clean-build)
>> 239M 240M 282M (After 3rd clean-build)
>> 285M 288M 283M (After 4th clean-build)
>> 289M 289M 287M (After 5th clean-build)
>> 291M 292M 289M (After 6th clean-build)
>>
>> Looks like the memory usage has an increase trend.
>>
>> I guess the "out of memory" problem I had is related to this memory usage
>> trend? What I normally do is saving the change I made to a class or advice
>> before I go to the next one. This saving would trigger a auto-build of the
>> project and increase the memory locked by the project.
>>
>> After a couple of "out of memory" crash, I clicked the "save" button more
>> often, which may make the situation even worse?
>>
>> Close the AspectJ project, the memory foot-print in the Win2k task manager
>> shrink back to 60M.
>>
>> Did a similiar "clean-build-all" test to my all other 7 java projects. The
>> memory usage foot-print was better. Relatively stable.
|
|
|
Goto Forum:
Current Time: Thu Dec 26 19:45:53 GMT 2024
Powered by FUDForum. Page generated in 0.04506 seconds |
] 
Search
Help
Register
Login
Home
