Eclipse Community Forums: Eclipse Platform

Home » Eclipse Projects » Eclipse Platform » M8 Vs M9 (your views)

Thu, 27 May 2004 07:26

Eclipse User

Hi Guys,

Just curious how many of us found the transition from M8 to M9 a pleasure in
terms of

- features
- performance
- UI responsiveness
- stability
- feel free to add more here on ...

cheers,

Re: M8 Vs M9 (your views) [message #246218 is a reply to message #246150]

Thu, 27 May 2004 08:17

Eclipse User

Hi Rahul,

Some initial thoughts:

> - features

R21 L&F - I don't use this as I like the new look and feel, but I think it's a
good thing and will hopefully put an end to a lot of very vocal discussions.

Browser widget on OS X - again, not something that I use but anything that
brings Eclipse closer to being a cross platofrm tool (at the moment there's
still a heavy Win32 bias, but it's improving) is a _very_ good thing. We just
need printing next (post 3.0 though).

Code folding - I quite like this, but there seem to be enough qwrinkles that the
developers have plenty of room to improve it in the 3.1 time frame.

> - performance
> - UI responsiveness

Seems faster on my machine. Being able to run more tasks in the background helps
the feeling of speed as well. I gather that this is one of the things we gained
by moving to OSGI, so that seems like a good decision now (I wasn't too sure at
first).

> - stability

No problems here.

> - feel free to add more here on ...

PDE still seems to bollox up build paths on your projects sometimes. :-(

Ian.

--
#ifndef __COMMON_SENSE__ | Ian Phillips
#include <std_disclaimer> | TIBCO Software Inc.
#endif | www.tibco.com

Re: M8 Vs M9 (your views) [message #246233 is a reply to message #246150]

Thu, 27 May 2004 09:40

Eclipse User

Originally posted by: rjs1956.hotmail.com

Actually I tried M8 and found enough problems that I went back to M7. M9 is
much better than M8 but it seems to eat up more memory than M7. When I use
eclipse to debug a large application it gets bogged down and runs out of
memory a lot faster than M7. I imagine there will be some performance
tweaking between now and the final 3.0 release.

"Rahul" <rahul.thakur@clear.net.nz> wrote in message
news:c94iqq$8gp$1@eclipse.org...
> Hi Guys,
>
> Just curious how many of us found the transition from M8 to M9 a pleasure
in
> terms of
>
> - features
> - performance
> - UI responsiveness
> - stability
> - feel free to add more here on ...
>
> cheers,
>
>

Re: M8 Vs M9 (your views) [message #246306 is a reply to message #246233]

Thu, 27 May 2004 10:35

Eclipse User

Originally posted by: mark.melvin.dspfactory.com

Bob Sullivan wrote:
> Actually I tried M8 and found enough problems that I went back to M7. M9 is
> much better than M8 but it seems to eat up more memory than M7. When I use
> eclipse to debug a large application it gets bogged down and runs out of
> memory a lot faster than M7. I imagine there will be some performance
> tweaking between now and the final 3.0 release.
>
>

I've used M6, M7, and M8 and never got an out of memory error. I have
already gotten 2 of them in M9 - which seems odd. I am not doing
anything more involved than before. I have 512MB RAM, and I typically
do not use any -vmargs switches. I never did on previous builds either...

Mark.

Re: M8 Vs M9 (your views) [message #246748 is a reply to message #246306]

Fri, 28 May 2004 05:29

Eclipse User

yeah, I think so too.
I think memory is one area that needs to be looked into before 3.0 is
released. I used be able to keep another application (IE for instance ) open
but with M9 even windows explorer takes like ages to come up.

apart from that I think there are still lot of issues that have to ironed
out. I happen to notice lost of preferences twice, and out of memory errors
(is 256MB RAM on XP too less for Eclipse) . It seems like with growing
number of projects in a workspace the memory requirements bloat up.

Can we not disable auto-build for other projects that are still in workspave
but not being worked upon (unless being referenced by the current project )
??

I still think M8 was snappier than M9. But it could be the feature and API
freeze for M9 didnt give much time to look into memory and UI responsiveness
issues. wondering if there are any config notes on tweaking Eclipse default
installation to make it cosume less memory and better perform.

I am sure lot of us are looking fwd to a release well worth all the wait :)

ciao,

rahul

"Mark Melvin" <mark.melvin@dspfactory.com> wrote in message
news:c94ttm$mu0$1@eclipse.org...
> Bob Sullivan wrote:
> > Actually I tried M8 and found enough problems that I went back to M7.
M9 is
> > much better than M8 but it seems to eat up more memory than M7. When I
use
> > eclipse to debug a large application it gets bogged down and runs out of
> > memory a lot faster than M7. I imagine there will be some performance
> > tweaking between now and the final 3.0 release.
> >
> >
>
> I've used M6, M7, and M8 and never got an out of memory error. I have
> already gotten 2 of them in M9 - which seems odd. I am not doing
> anything more involved than before. I have 512MB RAM, and I typically
> do not use any -vmargs switches. I never did on previous builds either...
>
> Mark.

Re: M8 Vs M9 (your views) [message #246787 is a reply to message #246748]

Fri, 28 May 2004 08:20

Eclipse User

In article <c970bm$9j1$1@eclipse.org>, rahul.thakur@clear.net.nz says...
> Can we not disable auto-build for other projects that are still in workspave
> but not being worked upon (unless being referenced by the current project )
> ??

You can close the projects you're not working on and that frees up some
mem, but you also lose refactoring and compilation of those projects
until you re-open them.

-- Scott

Re: M8 Vs M9 (your views) [message #247095 is a reply to message #246787]

Sat, 29 May 2004 00:29

Eclipse User

Originally posted by: smesh.openrules.com

Scott Stanchfield wrote:
>>Can we not disable auto-build for other projects that are still in workspave
>>but not being worked upon (unless being referenced by the current project )
>>??
>
>
> You can close the projects you're not working on and that frees up some
> mem, but you also lose refactoring and compilation of those projects
> until you re-open them.

I have huge memory consumption when *quick diff* is ON and I edit huge
files.

PS. It is ON by default.

--
Sam Mesh - http://openrules.com

Re: M8 Vs M9 (your views) [message #247172 is a reply to message #246306]

Sat, 29 May 2004 08:02

Eclipse User

yes memory eating behaviour is something that just did kreep in between m8 and m9

here is a gc dump that i have gathered when running eclipse with -verbose:gc over
time:

[Full GC 46233K->27083K(65152K), 0.7365581 secs]

[Full GC 94885K->51677K(101324K), 1.3020873 secs]

[Full GC 121646K->68468K(129848K), 1.3039020 secs]

[Full GC 122801K->102800K(131020K), 1.5458465 secs]
[GC 114320K->106355K(184264K), 0.0257915 secs]

Full GC 171569K->83939K(184520K), 1.5082001 secs]

is start default with -Xms64M that you can see the fist time a full GC
is recorderd after eclipse is fully up and running (it can hold everything
in 27M)
but after a while it grows and grows and the mem used after Full GC grows to 70-100M
and the total heap used is growing doubling
then after a while a full GC can drop the real mem usage back to 84M but not before
growing the heap to a 184M
But i still ask myself what is eclipse using/caching after its fully loaded and fully
build. With already java editors open ect. (so most plugins are also activated)
because after a while the real mem usage is x3 or even x4 (without projects being added)

johan

Mark Melvin wrote:

> Bob Sullivan wrote:
>
>> Actually I tried M8 and found enough problems that I went back to M7.
>> M9 is
>> much better than M8 but it seems to eat up more memory than M7. When
>> I use
>> eclipse to debug a large application it gets bogged down and runs out of
>> memory a lot faster than M7. I imagine there will be some performance
>> tweaking between now and the final 3.0 release.
>>
>>
>
> I've used M6, M7, and M8 and never got an out of memory error. I have
> already gotten 2 of them in M9 - which seems odd. I am not doing
> anything more involved than before. I have 512MB RAM, and I typically
> do not use any -vmargs switches. I never did on previous builds either...
>
> Mark.

Previous Topic:	Wiki updates
Next Topic:	XML - DTD Validator

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Jun 06 00:19:59 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter