|
|
|
|
| Re: eclipse profiler plugin 5.25 [message #61556 is a reply to message #60326] |
Thu, 19 June 2003 07: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 07:22 |
 bernhard schmidt
Messages: 15
Registered: July 2009 |
Junior Member |
|
|
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 09: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 #64634 is a reply to message #64587] |
Sun, 22 June 2003 15: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
|
|
|
Powered by
FUDForum. Page generated in 0.04619 seconds
] 
Search
Help
Register
Login
Home
