Skip to main content



      Home
Home » Eclipse Projects » Eclipse Platform » Profiling of a Java 1.5 Plugin
Profiling of a Java 1.5 Plugin [message #282931] Wed, 23 March 2005 17:48 Go to next message
Eclipse UserFriend
Hi there,

I need to profile a Java 1.5 Plugin (runtime).
The normal Eclipse Profiler fail on that purpose.
I am using Eclipse 3.1 M5.

Any idea how I can profile the plugin?
The plugin includes a complex view and a builder.


Cheers,

Martin (Kersten)
Re: Profiling of a Java 1.5 Plugin [message #282955 is a reply to message #282931] Thu, 24 March 2005 05:48 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: scheglov_ke.nlmk.ru

Martin Kersten:

> I need to profile a Java 1.5 Plugin (runtime).
> The normal Eclipse Profiler fail on that purpose.
> I am using Eclipse 3.1 M5.
Problem is that profiler uses BCEL for bytecode manipulations, and
AFAIK BCEL does not support 1.5 yet. May be I am wrong and it supports
it already?

>
> Any idea how I can profile the plugin?
> The plugin includes a complex view and a builder.


--
SY, Konstantin.
Advanced Eclipse SWT Designer (http://www.swt-designer.com)
Re: Profiling of a Java 1.5 Plugin [message #282967 is a reply to message #282931] Thu, 24 March 2005 07:35 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: Lamont_Gilbert.rigidsoftware.com

Martin Kersten wrote:
> Hi there,
>
> I need to profile a Java 1.5 Plugin (runtime).
> The normal Eclipse Profiler fail on that purpose.
> I am using Eclipse 3.1 M5.
>
> Any idea how I can profile the plugin?
> The plugin includes a complex view and a builder.
>
>
> Cheers,
>
> Martin (Kersten)
>
>

what is the normal Eclipse profiler?


CL
Re: Profiling of a Java 1.5 Plugin [message #282969 is a reply to message #282967] Thu, 24 March 2005 08:10 Go to previous messageGo to next message
Eclipse UserFriend
>> I need to profile a Java 1.5 Plugin (runtime).
>> The normal Eclipse Profiler fail on that purpose.
>> I am using Eclipse 3.1 M5.
>>
>> Any idea how I can profile the plugin?
>> The plugin includes a complex view and a builder.
>
> what is the normal Eclipse profiler?

Well there is a Eclipse plugin called Eclipse Profiler and it is quite
normal to check this out :-). Saidly the JDT folks didn't add
a profiler within the JDT plugin collection. Hopefully this
gets solved some days. It is surely a weakness for the IDE
to lack a tightly integrated profiler capability.


Cheers,

Martin (Kersten)
Re: Profiling of a Java 1.5 Plugin [message #282971 is a reply to message #282955] Thu, 24 March 2005 08:23 Go to previous messageGo to next message
Eclipse UserFriend
Hi Kosta,

>> I need to profile a Java 1.5 Plugin (runtime).
>> The normal Eclipse Profiler fail on that purpose.
>> I am using Eclipse 3.1 M5.

> Problem is that profiler uses BCEL for bytecode manipulations, and AFAIK
> BCEL does not support 1.5 yet. May be I am wrong and it supports it
> already?

Well I know but I also know that the JFluid stuff Sun
implemented also provides a way to profile a application.

BCEL 5.1 definitivly supports manipulation of 1.5 byte code. The
only thing I know, it does not provide any annotational support.

I don't know if the Eclipse Profiler depends on BCEL. Seams
like it does the stuff using the ProfilerDLL.dll.


Cheers,

Martin (Kersten)
Re: Profiling of a Java 1.5 Plugin [message #282973 is a reply to message #282971] Thu, 24 March 2005 08:56 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: scheglov_ke.nlmk.ru

Martin Kersten:

>>Problem is that profiler uses BCEL for bytecode manipulations, and AFAIK
>>BCEL does not support 1.5 yet. May be I am wrong and it supports it
>>already?
>
>
> Well I know but I also know that the JFluid stuff Sun
> implemented also provides a way to profile a application.
>
> BCEL 5.1 definitivly supports manipulation of 1.5 byte code. The
> only thing I know, it does not provide any annotational support.
Aha, so I have to update BCEL to make profiler work.
Thanks.

>
> I don't know if the Eclipse Profiler depends on BCEL. Seams
> like it does the stuff using the ProfilerDLL.dll.
In reallity I am author of this profiler, so... ;-)
ProfilerDLL.dll is used only to pass bytecode of class for
transformation in Java and pass it back to JVM. Most of logic is
implemented in Java. Only sampling is done in native, but it is rarely used.

--
SY, Konstantin.
Advanced Eclipse SWT Designer (http://www.swt-designer.com)
Re: Profiling of a Java 1.5 Plugin [message #282984 is a reply to message #282973] Thu, 24 March 2005 09:23 Go to previous messageGo to next message
Eclipse UserFriend
>> Well I know but I also know that the JFluid stuff Sun
>> implemented also provides a way to profile a application.
>>
>> BCEL 5.1 definitivly supports manipulation of 1.5 byte code. The
>> only thing I know, it does not provide any annotational support.

> Aha, so I have to update BCEL to make profiler work.
> Thanks.

I read the mailing archives and guys talked about how to create
and use generic informations using BCEL so I guess it is
1.5 ready (also there is no hint stating anything about compatibility
level in any way). So maybe my definitivly statement my be not
that definitifly :-). But they couldn't be talking about this if
it is not possible to do that :-). One thing that wonders me is,
BCEL 5.1 was released in the late 2003. I don't know what
kind of version policy they drive... .

>> I don't know if the Eclipse Profiler depends on BCEL. Seams
>> like it does the stuff using the ProfilerDLL.dll.

> In reallity I am author of this profiler, so... ;-)

I know. I have once talked to you two years ago! :-)

> ProfilerDLL.dll is used only to pass bytecode of class for
> transformation in Java and pass it back to JVM. Most of logic is
> implemented in Java. Only sampling is done in native, but it is rarely
> used.

Right. Can you use the JVMTI interface of Java 1.5? It sounds
like it is the right thing to do.

I often use Cglib for instrumenting purposes. Any idea about cglib?
I guess this is 1.5 ready in its 2.1 release (beside the cglib lacks this
information, too). If I remember correctly I do some class proxying
using cglib with JDK 1.5 code already. (Spring)

So please give me a call when Eclipse Profiler supports JDK 1.5
code. I would love to profile my application. ;-)


Cheers,

Martin (Kersten)
Re: Profiling of a Java 1.5 Plugin [message #283004 is a reply to message #282969] Thu, 24 March 2005 11:09 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: Lamont_Gilbert.rigidsoftware.com

Martin Kersten wrote:
>>> I need to profile a Java 1.5 Plugin (runtime).
>>>The normal Eclipse Profiler fail on that purpose.
>>>I am using Eclipse 3.1 M5.
>>>
>>>Any idea how I can profile the plugin?
>>>The plugin includes a complex view and a builder.
>>
>>what is the normal Eclipse profiler?
>
>
> Well there is a Eclipse plugin called Eclipse Profiler and it is quite
> normal to check this out :-). Saidly the JDT folks didn't add
> a profiler within the JDT plugin collection. Hopefully this
> gets solved some days. It is surely a weakness for the IDE
> to lack a tightly integrated profiler capability.
>
>
> Cheers,
>
> Martin (Kersten)
>
>

yes I see it now, looks nice. I have a need of heap profiling though
moreso than time profiling. The tool does not yet provide profiling to
catch memory leaks. It will be great when that is added.

I hear 1.5 is going to make this much easier.

CL
Re: Profiling of a Java 1.5 Plugin [message #283012 is a reply to message #283004] Thu, 24 March 2005 11:25 Go to previous messageGo to next message
Eclipse UserFriend
>>>> I need to profile a Java 1.5 Plugin (runtime).
>>>>The normal Eclipse Profiler fail on that purpose.
>>>>I am using Eclipse 3.1 M5.
>>>>
>>>>Any idea how I can profile the plugin?
>>>>The plugin includes a complex view and a builder.
>>>
>>>what is the normal Eclipse profiler?
>>
>>
>> Well there is a Eclipse plugin called Eclipse Profiler and it is quite
>> normal to check this out :-). Saidly the JDT folks didn't add
>> a profiler within the JDT plugin collection. Hopefully this
>> gets solved some days. It is surely a weakness for the IDE
>> to lack a tightly integrated profiler capability.

> yes I see it now, looks nice. I have a need of heap profiling though
> moreso than time profiling. The tool does not yet provide profiling to
> catch memory leaks. It will be great when that is added.
>
> I hear 1.5 is going to make this much easier.

Yeah. I tried to get various other profilers to work. My beloved
JProbe (brought the 3.0.8 version some years ago)
Is not able to handle the JDK 1.5 in the current version.

Currently I fiddle with the YourKit Java Profiler. It seams
to be possibly useable. This IVTMI interface seams to be
a great improvement (seams to not needing byte-code
instrumentation after all).


Cheers,

Martin (Kersten)
Re: Profiling of a Java 1.5 Plugin [message #283020 is a reply to message #283012] Thu, 24 March 2005 12:59 Go to previous messageGo to next message
Eclipse UserFriend
>>>>> I need to profile a Java 1.5 Plugin (runtime).
>>>>>The normal Eclipse Profiler fail on that purpose.
>>>>>I am using Eclipse 3.1 M5.
>>>>>
>>>>>Any idea how I can profile the plugin?
>>>>>The plugin includes a complex view and a builder.
>>>>
>>>>what is the normal Eclipse profiler?
>>>
>>>
>>> Well there is a Eclipse plugin called Eclipse Profiler and it is quite
>>> normal to check this out :-). Saidly the JDT folks didn't add
>>> a profiler within the JDT plugin collection. Hopefully this
>>> gets solved some days. It is surely a weakness for the IDE
>>> to lack a tightly integrated profiler capability.
>
>> yes I see it now, looks nice. I have a need of heap profiling though
>> moreso than time profiling. The tool does not yet provide profiling to
>> catch memory leaks. It will be great when that is added.
>>
>> I hear 1.5 is going to make this much easier.
>
> Yeah. I tried to get various other profilers to work. My beloved
> JProbe (brought the 3.0.8 version some years ago)
> Is not able to handle the JDK 1.5 in the current version.
>
> Currently I fiddle with the YourKit Java Profiler. It seams
> to be possibly useable. This IVTMI interface seams to be
> a great improvement (seams to not needing byte-code
> instrumentation after all).

The YourKit.com Java Profiler works with Eclipse 3.1 M5
(not with M4!). Works very well but I dont like the tree view
of the method invocations. I would like to have my beloved
JProbe views instead (caller+callee + simple table).


Cheers,

Martin (Kersten)
Re: Profiling of a Java 1.5 Plugin [message #283022 is a reply to message #282973] Thu, 24 March 2005 13:08 Go to previous messageGo to next message
Eclipse UserFriend
Hi Kosta,

>> I don't know if the Eclipse Profiler depends on BCEL. Seams
>> like it does the stuff using the ProfilerDLL.dll.
> In reallity I am author of this profiler, so... ;-)
> ProfilerDLL.dll is used only to pass bytecode of class for
> transformation in Java and pass it back to JVM. Most of logic is
> implemented in Java. Only sampling is done in native, but it is rarely
> used.

I got the YourKit.com Java Profiler to work. It works very well and
integreates seamlessly with Eclipse 3.1 M5.

Do you guys plan to provide a JVMTI implementation? It seams that
this interface is capable to provide the needed informations.


Cheers,

Martin (Kersten)
Re: Profiling of a Java 1.5 Plugin [message #283041 is a reply to message #282969] Thu, 24 March 2005 18:38 Go to previous message
Eclipse UserFriend
Originally posted by: neil.neil.swingler.name

Martin Kersten wrote:
>>> I need to profile a Java 1.5 Plugin (runtime).
>>>The normal Eclipse Profiler fail on that purpose.
>>>I am using Eclipse 3.1 M5.
>>>
>>>Any idea how I can profile the plugin?
>>>The plugin includes a complex view and a builder.
>>
>>what is the normal Eclipse profiler?
>
>
> Well there is a Eclipse plugin called Eclipse Profiler and it is quite
> normal to check this out :-). Saidly the JDT folks didn't add
> a profiler within the JDT plugin collection. Hopefully this
> gets solved some days. It is surely a weakness for the IDE
> to lack a tightly integrated profiler capability.
>
>
There is actually a profiler developed by the Eclipse project see
http://www.eclipse.org/tptp/index.html

I stumbled across this by accident - it is not very well publicised. The
engine seems to be pretty good and is capable of profiling an
application running at a fairly high CPU load. Unfortunately the
analysis tools are next to useless but are improving in the upcoming
releases. For the moment, I am using JFluid.

--
Neil Swingler
Previous Topic:JFace Viewer and InformationControlCreator
Next Topic:Find/Replace
Goto Forum:
  


Current Time: Wed May 14 18:06:56 EDT 2025

Powered by FUDForum. Page generated in 0.04424 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top