Eclipse Community Forums: Java Development Tools (JDT)

Home » Language IDEs » Java Development Tools (JDT) » eclipse profiler plugin 5.25

eclipse profiler plugin 5.25 [message #60326]

Wed, 18 June 2003 08:34

Eclipse User

hi

i am profiling my application with plugin. i found the plugin useful and
easy to use, especially profiling cpu and tasks. but profiling the heap
seems not to be the final.

- first it is very slow.

- i remarked also when i profile my application over a long time the
profiler stops getting heap probes.

- the memory indicated at the instance and heap window differs. for example
the heap windows shows the application uses 6M. The instance window for
example for byte[] complains more than 17M.

- it would be nice to see who references the instances.

best regards

benny

Re: eclipse profiler plugin 5.25 [message #60438 is a reply to message #60326]

Wed, 18 June 2003 09:49

Eclipse User

Are you referring to http://eclipsecolorer.sourceforge.net/ ?

Re: eclipse profiler plugin 5.25 [message #60938 is a reply to message #60438]

Wed, 18 June 2003 10:16

Eclipse User

hi vladimir

yes, sorry for my inexact formulation. you are the developper so far i know.
let me take the moment to say that the plugin helped me well to optimize the
application. its a fine work you dit.

best regards
benny

"Vladimir Blagojevic" <vladimir@cs.yorku.ca> wrote in message
news:bcpqlu$mvm$1@rogue.oti.com...
> Are you referring to http://eclipsecolorer.sourceforge.net/ ?
>
>

Re: eclipse profiler plugin 5.25 [message #60962 is a reply to message #60938]

Wed, 18 June 2003 10:22

Eclipse User

Not me Benny. Thank Konstantin Scheglov.

Cheers

"bernhard schmidt" <bernhard.schmidt@com-tec.ch> wrote in message
news:bcps3t$ol7$1@rogue.oti.com...
> hi vladimir
>
> yes, sorry for my inexact formulation. you are the developper so far i
know.
> let me take the moment to say that the plugin helped me well to optimize
the
> application. its a fine work you dit.
>
> best regards
> benny

Re: eclipse profiler plugin 5.25 [message #61556 is a reply to message #60326]

Thu, 19 June 2003 03:50

Eclipse User

Originally posted by: scheglov_ke.nlmk.ru

bernhard schmidt <bernhard.schmidt@com-tec.ch> wrote:

> i am profiling my application with plugin. i found the plugin useful and
> easy to use, especially profiling cpu and tasks. but profiling the heap
> seems not to be the final.

> - first it is very slow.
Yes, at is almost 2 times slower, than in OptimizeIt, and I don't
know how to speedup it. Most time is used for getting allocation
tree. I use JVMPI function GetCallTrace, and it is very slow. If you
know faster method, let me know. I will happy to add it.

> - i remarked also when i profile my application over a long time the
> profiler stops getting heap probes.
Well, may be there is some bug. Can you start your Eclipse with -debug
flag and look, may be there were messages on console?

> - the memory indicated at the instance and heap window differs. for example
> the heap windows shows the application uses 6M. The instance window for
> example for byte[] complains more than 17M.
Hm...

> - it would be nice to see who references the instances.
Yes, I have some code for heap dumping, but don't have enough
time for implementation of rest. And I think, that other profiling
related features like heap/thread/coverage profilings are not so
usefull as CPU profiling.

--
SY, Konstantin.

Re: eclipse profiler plugin 5.25 [message #62605 is a reply to message #61556]

Fri, 20 June 2003 03:22

Eclipse User

hi konstantin

i will do it the next time i use the tool.

for me is heap profiling very important to find memory leaks. in c++ i have
never problem with memory leaks, thanks to the language constructos of
destructor and new/delete operator overloading. in java the memory
management is left to the gc, which may be good for some kind of
application, but my experience is that for complex application you will have
memory leaks!

best regards

benny

"Konstantin Scheglov" <scheglov_ke@nlmk.ru> wrote in message
news:UbH23djNDHA.1496@fairy.ao.nlmk...
> bernhard schmidt <bernhard.schmidt@com-tec.ch> wrote:
>
>
> > i am profiling my application with plugin. i found the plugin useful and
> > easy to use, especially profiling cpu and tasks. but profiling the heap
> > seems not to be the final.
>
> > - first it is very slow.
> Yes, at is almost 2 times slower, than in OptimizeIt, and I don't
> know how to speedup it. Most time is used for getting allocation
> tree. I use JVMPI function GetCallTrace, and it is very slow. If you
> know faster method, let me know. I will happy to add it.
>
> > - i remarked also when i profile my application over a long time the
> > profiler stops getting heap probes.
> Well, may be there is some bug. Can you start your Eclipse with -debug
> flag and look, may be there were messages on console?
>
> > - the memory indicated at the instance and heap window differs. for
example
> > the heap windows shows the application uses 6M. The instance window for
> > example for byte[] complains more than 17M.
> Hm...
>
> > - it would be nice to see who references the instances.
> Yes, I have some code for heap dumping, but don't have enough
> time for implementation of rest. And I think, that other profiling
> related features like heap/thread/coverage profilings are not so
> usefull as CPU profiling.
>
> --
> SY, Konstantin.

Re: eclipse profiler plugin 5.25 [message #62702 is a reply to message #62605]

Fri, 20 June 2003 05:05

Eclipse User

Originally posted by: user.domain.invalid

bernhard schmidt wrote:

>
> for me is heap profiling very important to find memory leaks. in c++ i have
> never problem with memory leaks, thanks to the language constructos of
> destructor and new/delete operator overloading. in java the memory
> management is left to the gc, which may be good for some kind of
> application, but my experience is that for complex application you will have
> memory leaks!

Because you have an GC doesn't mean you have to do nothing to prevent
memory leaks. If you still hold references to objects not needed
anymore, you will have memory leaks for sure. But that's the same
problem in c++.

Funny that someone thinks that memory leaks are less likely in c++ than
in Java ;-)

Christoph

Re: eclipse profiler plugin 5.25 [message #62726 is a reply to message #62702]

Fri, 20 June 2003 05:20

Eclipse User

hi

i don't think that this it makes sense to discuss about the right way to do
memory management. what i will say is that the c++ has language constructs
that i miss in java. it is natural that all memory management is part of the
design and the language support it. this is not true in java. most time the
gc does the job for you - and this can also be a good thing, but at other
places you have to do it yourself, without support. further it is not always
easy to see at the first glance where to do it.

best regards
benny

<user@domain.invalid> wrote in message news:bcuir8$cip$1@rogue.oti.com...
> bernhard schmidt wrote:
>
> >
> > for me is heap profiling very important to find memory leaks. in c++ i
have
> > never problem with memory leaks, thanks to the language constructos of
> > destructor and new/delete operator overloading. in java the memory
> > management is left to the gc, which may be good for some kind of
> > application, but my experience is that for complex application you will
have
> > memory leaks!
>
> Because you have an GC doesn't mean you have to do nothing to prevent
> memory leaks. If you still hold references to objects not needed
> anymore, you will have memory leaks for sure. But that's the same
> problem in c++.
>
> Funny that someone thinks that memory leaks are less likely in c++ than
> in Java ;-)
>
> Christoph
>
>
>

Re: eclipse profiler plugin 5.25 [message #63177 is a reply to message #62726]

Fri, 20 June 2003 11:33

Eclipse User

Can you give me an example what you do when you have to do it yourself??

johan

>
> i don't think that this it makes sense to discuss about the right way to do
> memory management. what i will say is that the c++ has language constructs
> that i miss in java. it is natural that all memory management is part of the
> design and the language support it. this is not true in java. most time the
> gc does the job for you - and this can also be a good thing, but at other
> places you have to do it yourself, without support. further it is not always
> easy to see at the first glance where to do it.
>

Re: eclipse profiler plugin 5.25 [message #64355 is a reply to message #63177]

Sun, 22 June 2003 07:17

Eclipse User

hi

look at documentation describing the technology of garbage collectors and
especially documents of java gc. i am sure that you will find yorself cases
where the gc does not work. another place is to look at the sun site for
bugs. you will find bugs of the gc's or memory leaks of java library
functions!

i think most people could even ignore small memory leaks, but if you have
applications that run for months you have no choice other than check you
application.

best regards
benny

"Johan Compagner" <jcompagner@j-com.nl> wrote in message
news:bcv9h2$v60$1@rogue.oti.com...
> Can you give me an example what you do when you have to do it yourself??
>
> johan
>
> >
> > i don't think that this it makes sense to discuss about the right way to
do
> > memory management. what i will say is that the c++ has language
constructs
> > that i miss in java. it is natural that all memory management is part of
the
> > design and the language support it. this is not true in java. most time
the
> > gc does the job for you - and this can also be a good thing, but at
other
> > places you have to do it yourself, without support. further it is not
always
> > easy to see at the first glance where to do it.
> >
>
>

Re: eclipse profiler plugin 5.25 [message #64542 is a reply to message #64355]

Sun, 22 June 2003 11:00

Eclipse User

AmSun, 22 Jun 2003 13:17:46 +0200, "bernhard schmidt"
<bernhard.schmidt@com-tec.ch> wrote:

>look at documentation describing the technology of garbage collectors and
>especially documents of java gc. i am sure that you will find yorself cases
>where the gc does not work. another place is to look at the sun site for

Could describe a case where no gc can decide wether a reference
is used or not?

>bugs. you will find bugs of the gc's or memory leaks of java library
>functions!

Bugs are a different thing. You will find them in every c++ lib as
well.

>i think most people could even ignore small memory leaks, but if you have
>applications that run for months you have no choice other than check you
>application.

Nothing different than c++.

martin

Re: eclipse profiler plugin 5.25 [message #64587 is a reply to message #64542]

Sun, 22 June 2003 11:15

Eclipse User

hi

sorry, but i don't know what the aim of this discussion shall be. the thread
started because i wrote that checking an application for memory leak is
important for me. i got an answer from someone that i could not let without
reply; that is all. each language has idioms and i learned not only to life
with it, but to think in that language. i have no "bock" to discuss what is
better in one language than in the other. more, such a discussion has
nothing to do in this forum.

regards
benny

"Martin M

Re: eclipse profiler plugin 5.25 [message #64634 is a reply to message #64587]

Sun, 22 June 2003 11:50

Eclipse User

Originally posted by: vkyr.nospam-ision.net

Bernhard, actually you can only detect possible memory leaks (dangling
references) the easy way with other suitable tools (OptimizeIt, JProbe
etc.). It seems Konstattin doesn't have actually the time to introduce such
a feature.

Usually for detecting mem leaks in some user controllable manner, the
eclipse profiler would need to have some take snapshots after GC mechanism
and also coresponding snapshot diff/compare features. Further, the eclipse
profiler would also need some algorithm, which could compare the instance
counts and used mem of all related objects between those snapshots, those
which differ significantly would have to be marked and visually showup for a
fine grade inspection.

-vkyr

"bernhard schmidt" <bernhard.schmidt@com-tec.ch> schrieb im Newsbeitrag
news:bd4h26$q20$1@rogue.oti.com...
> hi
>
> sorry, but i don't know what the aim of this discussion shall be. the
thread
> started because i wrote that checking an application for memory leak is
> important for me. i got an answer from someone that i could not let
without
> reply; that is all. each language has idioms and i learned not only to
life
> with it, but to think in that language. i have no "bock" to discuss what
is
> better in one language than in the other. more, such a discussion has
> nothing to do in this forum.
>
> regards
> benny
>
>
>
> "Martin M

Previous Topic:	Compile One Java File- That's it!
Next Topic:	XML Tree Viewer source

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Oct 31 04:37:55 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter