Home » Eclipse Projects » Eclipse Platform » [ANN] Eclipse profiler plugin, 0.5.20
| [ANN] Eclipse profiler plugin, 0.5.20 [message #29774] |
Mon, 12 May 2003 04:07  |
Eclipse User |
|
|
|
Originally posted by: scheglov_ke.nlmk.ru
http://eclipsecolorer.sourceforge.net
12 May 2003 - Version 0.5.20
--------------------------
[+] Button "Save statistics" added to "Threads" view. It allows you
save current statistics in project (in folder "profiles"). Later
you will able to open them using doubleclick on file. Name of
file constructed from name of launch configuration plus date/time
when save pressed plus extention ".profile". This allows you to
analyze statistics later without incurring the performance penalty of
profiling when you really want to review the stats.
[+] If you profile applications with JDK 1.4+, then when you stop profiling
using "Stop profiling" button on "Threads" view, profiler will avoid
most overhead, so in result application run only 30% slower (!), then
without profiling at all. Same is true if you start profiling with
disabled auto start. I think, that with such low slowdown it is
possible
to start applications almost always with profiling and activate it
only when you want to gather statistics. After this you can stop
profiling
and your application will work fast again. This is especially usefull
for
such long runned applications as Tomcat and JBoss.
Limitation for Java 1.4 is related with method
Throwable.getStackTrace(), without this method I can not restore call
stack and all call stack base statistics (thread call stack, call
graph)
will be wrong. So, I decided to disable this feature with JDK lower
than 1.4.
[+] Export thread call graph to GIF/PNG/JPG added.
[+] Export thread call tree in HTML JavaScript tree.
|
|
|
| Re: [ANN] Eclipse profiler plugin, 0.5.20 [message #29792 is a reply to message #29774] |
Mon, 12 May 2003 07:42  |
| Eclipse User |
|
|
|
Originally posted by: sddg.yahoo.com
Do you know of any other profiler plugins?
"Konstantin Scheglov" <scheglov_ke@nlmk.ru> wrote in message
news:b9nkn7$9m4$1@rogue.oti.com...
> http://eclipsecolorer.sourceforge.net
>
> 12 May 2003 - Version 0.5.20
> --------------------------
> [+] Button "Save statistics" added to "Threads" view. It allows you
> save current statistics in project (in folder "profiles"). Later
> you will able to open them using doubleclick on file. Name of
> file constructed from name of launch configuration plus date/time
> when save pressed plus extention ".profile". This allows you to
> analyze statistics later without incurring the performance penalty of
> profiling when you really want to review the stats.
> [+] If you profile applications with JDK 1.4+, then when you stop
profiling
> using "Stop profiling" button on "Threads" view, profiler will avoid
> most overhead, so in result application run only 30% slower (!), then
> without profiling at all. Same is true if you start profiling with
> disabled auto start. I think, that with such low slowdown it is
> possible
> to start applications almost always with profiling and activate it
> only when you want to gather statistics. After this you can stop
> profiling
> and your application will work fast again. This is especially usefull
> for
> such long runned applications as Tomcat and JBoss.
> Limitation for Java 1.4 is related with method
> Throwable.getStackTrace(), without this method I can not restore call
> stack and all call stack base statistics (thread call stack, call
> graph)
> will be wrong. So, I decided to disable this feature with JDK lower
> than 1.4.
> [+] Export thread call graph to GIF/PNG/JPG added.
> [+] Export thread call tree in HTML JavaScript tree.
>
>
|
|
|
| Re: [ANN] Eclipse profiler plugin, 0.5.20 [message #29796 is a reply to message #29792] |
Mon, 12 May 2003 08:00 |
| Eclipse User |
|
|
|
Originally posted by: scheglov_ke.nlmk.ru
Sui Ma wrote:
> Do you know of any other profiler plugins?
Why? :-)
Do you have problems with this plugin?
There is another free plugin, it uses standard HPROF as profiling
engine. So, it works with more platforms, but much slower and has not so
much features.
http://jmechanic.sourceforge.net
> "Konstantin Scheglov" <scheglov_ke@nlmk.ru> wrote in message
> news:b9nkn7$9m4$1@rogue.oti.com...
> > http://eclipsecolorer.sourceforge.net
> >
> > 12 May 2003 - Version 0.5.20
> > --------------------------
> > [+] Button "Save statistics" added to "Threads" view. It allows you
> > save current statistics in project (in folder "profiles"). Later
> > you will able to open them using doubleclick on file. Name of
> > file constructed from name of launch configuration plus date/time
> > when save pressed plus extention ".profile". This allows you to
> > analyze statistics later without incurring the performance penalty of
> > profiling when you really want to review the stats.
> > [+] If you profile applications with JDK 1.4+, then when you stop
> profiling
> > using "Stop profiling" button on "Threads" view, profiler will avoid
> > most overhead, so in result application run only 30% slower (!), then
> > without profiling at all. Same is true if you start profiling with
> > disabled auto start. I think, that with such low slowdown it is
> > possible
> > to start applications almost always with profiling and activate it
> > only when you want to gather statistics. After this you can stop
> > profiling
> > and your application will work fast again. This is especially usefull
> > for
> > such long runned applications as Tomcat and JBoss.
> > Limitation for Java 1.4 is related with method
> > Throwable.getStackTrace(), without this method I can not restore call
> > stack and all call stack base statistics (thread call stack, call
> > graph)
> > will be wrong. So, I decided to disable this feature with JDK lower
> > than 1.4.
> > [+] Export thread call graph to GIF/PNG/JPG added.
> > [+] Export thread call tree in HTML JavaScript tree.
> >
> >
|
|
|
| Re: [ANN] Eclipse profiler plugin, 0.5.20 [message #29814 is a reply to message #29796] |
Mon, 12 May 2003 10:14 |
| Eclipse User |
|
|
|
Originally posted by: sddg.yahoo.com
no, this one is just fine :)
It helped me a lot optimizing my application
just to compare
"Konstantin Scheglov" <scheglov_ke@nlmk.ru> wrote in message
news:b9o2cd$kab$1@rogue.oti.com...
> Sui Ma wrote:
>
> > Do you know of any other profiler plugins?
> Why? :-)
> Do you have problems with this plugin?
>
> There is another free plugin, it uses standard HPROF as profiling
> engine. So, it works with more platforms, but much slower and has not so
> much features.
> http://jmechanic.sourceforge.net
>
> > "Konstantin Scheglov" <scheglov_ke@nlmk.ru> wrote in message
> > news:b9nkn7$9m4$1@rogue.oti.com...
> > > http://eclipsecolorer.sourceforge.net
> > >
> > > 12 May 2003 - Version 0.5.20
> > > --------------------------
> > > [+] Button "Save statistics" added to "Threads" view. It allows you
> > > save current statistics in project (in folder "profiles"). Later
> > > you will able to open them using doubleclick on file. Name of
> > > file constructed from name of launch configuration plus date/time
> > > when save pressed plus extention ".profile". This allows you to
> > > analyze statistics later without incurring the performance penalty
of
> > > profiling when you really want to review the stats.
> > > [+] If you profile applications with JDK 1.4+, then when you stop
> > profiling
> > > using "Stop profiling" button on "Threads" view, profiler will
avoid
> > > most overhead, so in result application run only 30% slower (!),
then
> > > without profiling at all. Same is true if you start profiling with
> > > disabled auto start. I think, that with such low slowdown it is
> > > possible
> > > to start applications almost always with profiling and activate it
> > > only when you want to gather statistics. After this you can stop
> > > profiling
> > > and your application will work fast again. This is especially
usefull
> > > for
> > > such long runned applications as Tomcat and JBoss.
> > > Limitation for Java 1.4 is related with method
> > > Throwable.getStackTrace(), without this method I can not restore
call
> > > stack and all call stack base statistics (thread call stack, call
> > > graph)
> > > will be wrong. So, I decided to disable this feature with JDK
lower
> > > than 1.4.
> > > [+] Export thread call graph to GIF/PNG/JPG added.
> > > [+] Export thread call tree in HTML JavaScript tree.
> > >
> > >
>
>
>
>
>
|
|
|
| Re: [ANN] Eclipse profiler plugin, 0.5.20 [message #29839 is a reply to message #29774] |
Mon, 12 May 2003 14:10 |
| Eclipse User |
|
|
|
Originally posted by: vkyr.nospam-ision.net
Konstantin, your Eclipse profiler plugin is getting better and better. It's
a nice and valuable plugin. - For the future it might be nice to have build
in some snapshot and snapshot compare capability. This way, you could
make/save snapshots of different profiling states and then use the compare
in order to detect possible memory leaks. - This would then be similar to
what for example Borland's OptimizeIt offers with it's build in memory leak
finding facility.
Keep on the great work, greetings Valentino!
"Konstantin Scheglov" <scheglov_ke@nlmk.ru> schrieb im Newsbeitrag
news:b9nkn7$9m4$1@rogue.oti.com...
> http://eclipsecolorer.sourceforge.net
>
> 12 May 2003 - Version 0.5.20
> --------------------------
> [+] Button "Save statistics" added to "Threads" view. It allows you
> save current statistics in project (in folder "profiles"). Later
> you will able to open them using doubleclick on file. Name of
> file constructed from name of launch configuration plus date/time
> when save pressed plus extention ".profile". This allows you to
> analyze statistics later without incurring the performance penalty of
> profiling when you really want to review the stats.
> [+] If you profile applications with JDK 1.4+, then when you stop
profiling
> using "Stop profiling" button on "Threads" view, profiler will avoid
> most overhead, so in result application run only 30% slower (!), then
> without profiling at all. Same is true if you start profiling with
> disabled auto start. I think, that with such low slowdown it is
> possible
> to start applications almost always with profiling and activate it
> only when you want to gather statistics. After this you can stop
> profiling
> and your application will work fast again. This is especially usefull
> for
> such long runned applications as Tomcat and JBoss.
> Limitation for Java 1.4 is related with method
> Throwable.getStackTrace(), without this method I can not restore call
> stack and all call stack base statistics (thread call stack, call
> graph)
> will be wrong. So, I decided to disable this feature with JDK lower
> than 1.4.
> [+] Export thread call graph to GIF/PNG/JPG added.
> [+] Export thread call tree in HTML JavaScript tree.
>
>
|
|
| |
| Re: [ANN] Eclipse profiler plugin, 0.5.20 [message #29879 is a reply to message #29839] |
Tue, 13 May 2003 04:13 |
| Eclipse User |
|
|
|
Originally posted by: scheglov_ke.nlmk.ru
Valentino Kyriakides wrote:
Yes, I have idea to compare statistics, but I think only about CPU
statistics. Of course I can compare only percents of invocation count and
direct time, because user can make snapshot in any moment. And even in
this case I am not sure about implementation details.
About heap. There is already button "Mark instances" in "Instances" view.
> Konstantin, your Eclipse profiler plugin is getting better and better. It's
> a nice and valuable plugin. - For the future it might be nice to have build
> in some snapshot and snapshot compare capability. This way, you could
> make/save snapshots of different profiling states and then use the compare
> in order to detect possible memory leaks. - This would then be similar to
> what for example Borland's OptimizeIt offers with it's build in memory leak
> finding facility.
> Keep on the great work, greetings Valentino!
> "Konstantin Scheglov" <scheglov_ke@nlmk.ru> schrieb im Newsbeitrag
> news:b9nkn7$9m4$1@rogue.oti.com...
> > http://eclipsecolorer.sourceforge.net
> >
> > 12 May 2003 - Version 0.5.20
> > --------------------------
> > [+] Button "Save statistics" added to "Threads" view. It allows you
> > save current statistics in project (in folder "profiles"). Later
> > you will able to open them using doubleclick on file. Name of
> > file constructed from name of launch configuration plus date/time
> > when save pressed plus extention ".profile". This allows you to
> > analyze statistics later without incurring the performance penalty of
> > profiling when you really want to review the stats.
> > [+] If you profile applications with JDK 1.4+, then when you stop
> profiling
> > using "Stop profiling" button on "Threads" view, profiler will avoid
> > most overhead, so in result application run only 30% slower (!), then
> > without profiling at all. Same is true if you start profiling with
> > disabled auto start. I think, that with such low slowdown it is
> > possible
> > to start applications almost always with profiling and activate it
> > only when you want to gather statistics. After this you can stop
> > profiling
> > and your application will work fast again. This is especially usefull
> > for
> > such long runned applications as Tomcat and JBoss.
> > Limitation for Java 1.4 is related with method
> > Throwable.getStackTrace(), without this method I can not restore call
> > stack and all call stack base statistics (thread call stack, call
> > graph)
> > will be wrong. So, I decided to disable this feature with JDK lower
> > than 1.4.
> > [+] Export thread call graph to GIF/PNG/JPG added.
> > [+] Export thread call tree in HTML JavaScript tree.
> >
> >
|
|
| | |
| Re: [ANN] Eclipse profiler plugin, 0.5.20 [message #29908 is a reply to message #29905] |
Tue, 13 May 2003 06:27 |
| Eclipse User |
|
|
|
Originally posted by: scheglov_ke.nlmk.ru
Jan Schulz wrote:
> >> Do you have any plans to integrate hyades into your tool?
> > I've just looked on Hyades - looks fairly complex.
> > What do you mean under integration?
> Hyades will provide a framework for testing and I think also some
> parts will be for profiling. All the data will then collected and
> stored/computed/whatever (at least thats my understanding from
> reading the newsgroup...). As your plugin does also some data
> collection and this graphs...
Ok, I understand your point.
I don't think, that I will start integration right now. It is currently
not obvious, where this project going to, they still write "vision
document".
--
SY, Kosta.
|
|
|
Goto Forum:
Current Time: Mon Apr 28 03:10:16 EDT 2025
Powered by FUDForum. Page generated in 0.04224 seconds |
Home