| Slowdown with large projects [message #100047] |
Sun, 18 April 2004 19:19  |
Eclipse User |
|
|
|
Originally posted by: bmentink.trimble.co.nz
Hi all,
When we have a large C/C++ project loaded, we get massive interrmittant
slowdowns. i.e the java runtime goes to 99% for a period of time
and sometimes eclipse can crash and/or with a memory error.
I have also seen a "java heap" error on loading the large project
directory.
Eclipse seems to use a massive amount of RAM, with no projects about 50Mb,
with the mentioned project loaded, about 107Mb ... is this normal?
Are we seeing a memory problem, or is it something else.
I will post this to the Eclipse forum as well, as I don't know if it
is a Eclipse problem, or with the C/C++ plugin itself.
Thanks,
Bernie Mentink
|
|
|
|
| Re: Slowdown with large projects [message #100267 is a reply to message #100120] |
Mon, 19 April 2004 17:58  |
| Eclipse User |
|
|
|
Originally posted by: bmentink.trimble.co.nz
Hi Alex,
I am using version 3.0M8 and the corresponding M8 version off CDT. Running
it
on a WinNT 2000 system. I suspect the problem is the "indexing" problem
mentioned elsewhere in the newsgroup.
Cheers,
Bernie
Alex Klein wrote:
> Hi Bernie,
> I've got that too using Eclipse 2.1, but I'm not sure if eclipse 3.0
> also has that problem. From the short time I looked into eclipse 3, it
> seemed to have a much better performance. Could not test it on a larger
> project as I have some problems with 3.0M8 as posted in another thread
> (from which the most current is that the build-output does not show up
> in the console ... any ideas on that yet?). Maybe it helps if you post
> your OS and eclipse version.
> Most notably, the problem shows up when saving a file or doing a build.
> Simply saving a file sometimes is quite fast, but more often it takes up
> to half a minute. When building, updating of the project after the build
> is complete may also take half a minute. Don't know what exactely causes
> it...
> I use Suse 8.2 with J2SDK1.4.2_04 from Sun, Eclipse 2.1.2 and CDT 1.2.0.
> The project is about 5000 lines of code and the whole workspace is about
> 70MB including binaries and data files. Hope that helps to narrow it down...
> Alex
|
|
|
| Re: Slowdown with large projects [message #100349 is a reply to message #100267] |
Tue, 20 April 2004 09:47 |
| Eclipse User |
|
|
|
Bernie Mentink wrote:
> Hi Alex,
>
> I am using version 3.0M8 and the corresponding M8 version off CDT. Running
> it
> on a WinNT 2000 system. I suspect the problem is the "indexing" problem
> mentioned elsewhere in the newsgroup.
I'm seeing exactly what you're seeing. 3.0M8, Win2000, and up to 107MB
or so of memory in use by javaw.exe and stretches of several minutes
where it uses 99% of the CPU. I routinely have 5-10 files open at a
time. I don't think I saw anything like that with Eclipse 2.1, this is
different from that problem that kept updating the Outline.
Cheers,
Rick
>
> Cheers,
> Bernie
>
> Alex Klein wrote:
>
>
>>Hi Bernie,
>>I've got that too using Eclipse 2.1, but I'm not sure if eclipse 3.0
>>also has that problem. From the short time I looked into eclipse 3, it
>>seemed to have a much better performance. Could not test it on a larger
>>project as I have some problems with 3.0M8 as posted in another thread
>>(from which the most current is that the build-output does not show up
>>in the console ... any ideas on that yet?). Maybe it helps if you post
>>your OS and eclipse version.
>
>
>>Most notably, the problem shows up when saving a file or doing a build.
>>Simply saving a file sometimes is quite fast, but more often it takes up
>>to half a minute. When building, updating of the project after the build
>>is complete may also take half a minute. Don't know what exactely causes
>>it...
>>I use Suse 8.2 with J2SDK1.4.2_04 from Sun, Eclipse 2.1.2 and CDT 1.2.0.
>>The project is about 5000 lines of code and the whole workspace is about
>>70MB including binaries and data files. Hope that helps to narrow it down...
>
>
>>Alex
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.05151 seconds
Home