Home » Eclipse Projects » Eclipse Platform » [ANN] Eclipse profiler plugin, 0.5.25
| [ANN] Eclipse profiler plugin, 0.5.25 [message #75072] |
Mon, 16 June 2003 04:21  |
Eclipse User |
|
|
|
Originally posted by: scheglov_ke.nlmk.ru
http://eclipsecolorer.sourceforge.net
16 Jun 2003 - Version 0.5.25
--------------------------
[-] Bug with LDC/LDC_W in BCEL fixed. I hope, that this is reason, why
JVM throws "VerifyError: Illegal constant pool index".
[+] Now you can use doubleclick in Packages/Classes/Methods views to
open method in editor. Context menu was not very convinient way.
[+] "Live" thread call graph. Now it refreshes automatically, as any other
profiler view. "Refresh" button removed.
[+] New filters for thread call graph. You can set, that you want to
see control flows with at least 1% of total time, or 2%, 3%, 5%, 10%.
This allows remove most of not interesting details like methods,
which were called only once, or don't use much time.
[+] "Pause CPU profiling on method leave" option in launch configuration
dialog. When it is on, profiler will stop gathering statistics and
resume when control flow will enter in this method again. This allows
you profile only part of application, without parts, which do other
things, like preparing data for interesting part.
[-] Fixed crash in ProfilerDLL during heap profiling. Does anybody knows
why OptimizeIt is 2 times faster when does heap profiling? It seems, that
most slow part is getting allocation trace, and it is in JVM. I don't
know, how to make it faster. :-(
--
SY, Konstantin.
|
|
|
| Re: [ANN] Eclipse profiler plugin, 0.5.25 [message #75089 is a reply to message #75072] |
Mon, 16 June 2003 07:58  |
 Christian Sell
Messages: 77
Registered: July 2009 |
Member |
|
|
Hi Konstantin,
I already posted this on the mailing list.. I am missing an option to
pause the program being profiled remotely until the profiler connects to
it. This is important for standalone programs (i.e., non-appserver)
which otherwise may just run through from start to stop. Unfortunately,
under Linux I can only use the remote profiler.
thanks,
Christian
Konstantin Scheglov wrote:
> http://eclipsecolorer.sourceforge.net
>
> 16 Jun 2003 - Version 0.5.25
> --------------------------
> [-] Bug with LDC/LDC_W in BCEL fixed. I hope, that this is reason, why
> JVM throws "VerifyError: Illegal constant pool index".
> [+] Now you can use doubleclick in Packages/Classes/Methods views to
> open method in editor. Context menu was not very convinient way.
> [+] "Live" thread call graph. Now it refreshes automatically, as any other
> profiler view. "Refresh" button removed.
> [+] New filters for thread call graph. You can set, that you want to
> see control flows with at least 1% of total time, or 2%, 3%, 5%, 10%.
> This allows remove most of not interesting details like methods,
> which were called only once, or don't use much time.
> [+] "Pause CPU profiling on method leave" option in launch configuration
> dialog. When it is on, profiler will stop gathering statistics and
> resume when control flow will enter in this method again. This allows
> you profile only part of application, without parts, which do other
> things, like preparing data for interesting part.
> [-] Fixed crash in ProfilerDLL during heap profiling. Does anybody knows
> why OptimizeIt is 2 times faster when does heap profiling? It seems, that
> most slow part is getting allocation trace, and it is in JVM. I don't
> know, how to make it faster. :-(
>
>
|
|
|
| Re: [ANN] Eclipse profiler plugin, 0.5.25 [message #75179 is a reply to message #75089] |
Mon, 16 June 2003 10:07 |
| Eclipse User |
|
|
|
Originally posted by: scheglov_ke.nlmk.ru
Christian Sell <cse@dynabean.de> wrote:
You always can start test application locally and look, which
options are used.
In you case you should add:
-D__PROFILER_WAIT_FRONTEND_CONNECT=1
(it is 0 by default, i.e. allow application to run, even
there is no frontend connected).
> I already posted this on the mailing list.. I am missing an option to
> pause the program being profiled remotely until the profiler connects to
> it. This is important for standalone programs (i.e., non-appserver)
> which otherwise may just run through from start to stop. Unfortunately,
> under Linux I can only use the remote profiler.
> thanks,
> Christian
> Konstantin Scheglov wrote:
>> http://eclipsecolorer.sourceforge.net
>>
>> 16 Jun 2003 - Version 0.5.25
>> --------------------------
>> [-] Bug with LDC/LDC_W in BCEL fixed. I hope, that this is reason, why
>> JVM throws "VerifyError: Illegal constant pool index".
>> [+] Now you can use doubleclick in Packages/Classes/Methods views to
>> open method in editor. Context menu was not very convinient way.
>> [+] "Live" thread call graph. Now it refreshes automatically, as any other
>> profiler view. "Refresh" button removed.
>> [+] New filters for thread call graph. You can set, that you want to
>> see control flows with at least 1% of total time, or 2%, 3%, 5%, 10%.
>> This allows remove most of not interesting details like methods,
>> which were called only once, or don't use much time.
>> [+] "Pause CPU profiling on method leave" option in launch configuration
>> dialog. When it is on, profiler will stop gathering statistics and
>> resume when control flow will enter in this method again. This allows
>> you profile only part of application, without parts, which do other
>> things, like preparing data for interesting part.
>> [-] Fixed crash in ProfilerDLL during heap profiling. Does anybody knows
>> why OptimizeIt is 2 times faster when does heap profiling? It seems, that
>> most slow part is getting allocation trace, and it is in JVM. I don't
>> know, how to make it faster. :-(
>>
>>
--
SY, Konstantin.
|
|
|
| Re: [ANN] Eclipse profiler plugin, 0.5.25 [message #75230 is a reply to message #75179] |
Mon, 16 June 2003 10:46 |
Christian Sell
Messages: 77
Registered: July 2009 |
Member |
|
|
Konstantin Scheglov wrote:
> Christian Sell <cse@dynabean.de> wrote:
>
>
> You always can start test application locally and look, which
> options are used.
start locally? what do you mean? look where?
> In you case you should add:
> -D__PROFILER_WAIT_FRONTEND_CONNECT=1
> (it is 0 by default, i.e. allow application to run, even
> there is no frontend connected).
is there documentation anywhere on the recognized options?
thanks,
Christian
>
>
>>I already posted this on the mailing list.. I am missing an option to
>>pause the program being profiled remotely until the profiler connects to
>>it. This is important for standalone programs (i.e., non-appserver)
>>which otherwise may just run through from start to stop. Unfortunately,
>>under Linux I can only use the remote profiler.
>
>
>>thanks,
>>Christian
>
>
>>Konstantin Scheglov wrote:
>>
>>>http://eclipsecolorer.sourceforge.net
>>>
>>>16 Jun 2003 - Version 0.5.25
>>>--------------------------
>>>[-] Bug with LDC/LDC_W in BCEL fixed. I hope, that this is reason, why
>>> JVM throws "VerifyError: Illegal constant pool index".
>>>[+] Now you can use doubleclick in Packages/Classes/Methods views to
>>> open method in editor. Context menu was not very convinient way.
>>>[+] "Live" thread call graph. Now it refreshes automatically, as any other
>>> profiler view. "Refresh" button removed.
>>>[+] New filters for thread call graph. You can set, that you want to
>>> see control flows with at least 1% of total time, or 2%, 3%, 5%, 10%.
>>> This allows remove most of not interesting details like methods,
>>> which were called only once, or don't use much time.
>>>[+] "Pause CPU profiling on method leave" option in launch configuration
>>> dialog. When it is on, profiler will stop gathering statistics and
>>> resume when control flow will enter in this method again. This allows
>>> you profile only part of application, without parts, which do other
>>> things, like preparing data for interesting part.
>>>[-] Fixed crash in ProfilerDLL during heap profiling. Does anybody knows
>>> why OptimizeIt is 2 times faster when does heap profiling? It seems, that
>>> most slow part is getting allocation trace, and it is in JVM. I don't
>>> know, how to make it faster. :-(
>>>
>>>
>
>
>
|
|
|
| Re: [ANN] Eclipse profiler plugin, 0.5.25 [message #75277 is a reply to message #75230] |
Mon, 16 June 2003 11:42 |
| Eclipse User |
|
|
|
Originally posted by: scheglov_ke.nlmk.ru
Christian Sell <cse@dynabean.de> wrote:
>> You always can start test application locally and look, which
>> options are used.
> start locally? what do you mean? look where?
I mean start in Eclipse.
>> In you case you should add:
>> -D__PROFILER_WAIT_FRONTEND_CONNECT=1
>> (it is 0 by default, i.e. allow application to run, even
>> there is no frontend connected).
> is there documentation anywhere on the recognized options?
No.
> thanks,
> Christian
>>
>>
>>>I already posted this on the mailing list.. I am missing an option to
>>>pause the program being profiled remotely until the profiler connects to
>>>it. This is important for standalone programs (i.e., non-appserver)
>>>which otherwise may just run through from start to stop. Unfortunately,
>>>under Linux I can only use the remote profiler.
>>
>>
>>>thanks,
>>>Christian
>>
>>
>>>Konstantin Scheglov wrote:
>>>
>>>>http://eclipsecolorer.sourceforge.net
>>>>
>>>>16 Jun 2003 - Version 0.5.25
>>>>--------------------------
>>>>[-] Bug with LDC/LDC_W in BCEL fixed. I hope, that this is reason, why
>>>> JVM throws "VerifyError: Illegal constant pool index".
>>>>[+] Now you can use doubleclick in Packages/Classes/Methods views to
>>>> open method in editor. Context menu was not very convinient way.
>>>>[+] "Live" thread call graph. Now it refreshes automatically, as any other
>>>> profiler view. "Refresh" button removed.
>>>>[+] New filters for thread call graph. You can set, that you want to
>>>> see control flows with at least 1% of total time, or 2%, 3%, 5%, 10%.
>>>> This allows remove most of not interesting details like methods,
>>>> which were called only once, or don't use much time.
>>>>[+] "Pause CPU profiling on method leave" option in launch configuration
>>>> dialog. When it is on, profiler will stop gathering statistics and
>>>> resume when control flow will enter in this method again. This allows
>>>> you profile only part of application, without parts, which do other
>>>> things, like preparing data for interesting part.
>>>>[-] Fixed crash in ProfilerDLL during heap profiling. Does anybody knows
>>>> why OptimizeIt is 2 times faster when does heap profiling? It seems, that
>>>> most slow part is getting allocation trace, and it is in JVM. I don't
>>>> know, how to make it faster. :-(
>>>>
>>>>
>>
>>
>>
--
SY, Konstantin.
|
|
| |
| Re: [ANN] Eclipse profiler plugin, 0.5.25 [message #75342 is a reply to message #75277] |
Mon, 16 June 2003 12:17 |
Christian Sell
Messages: 77
Registered: July 2009 |
Member |
|
|
Konstantin Scheglov wrote:
> Christian Sell <cse@dynabean.de> wrote:
>
>
>>> You always can start test application locally and look, which
>>>options are used.
>>
>>start locally? what do you mean? look where?
>
> I mean start in Eclipse.
not possible under Linux, right?
>
>
>>> In you case you should add:
>>> -D__PROFILER_WAIT_FRONTEND_CONNECT=1
>>> (it is 0 by default, i.e. allow application to run, even
>>>there is no frontend connected).
>>
>>is there documentation anywhere on the recognized options?
>
> No.
>
>
>
>>thanks,
>>Christian
>
>
>>>
>>>>I already posted this on the mailing list.. I am missing an option to
>>>>pause the program being profiled remotely until the profiler connects to
>>>>it. This is important for standalone programs (i.e., non-appserver)
>>>>which otherwise may just run through from start to stop. Unfortunately,
>>>>under Linux I can only use the remote profiler.
>>>
>>>
>>>>thanks,
>>>>Christian
>>>
>>>
>>>>Konstantin Scheglov wrote:
>>>>
>>>>
>>>>>http://eclipsecolorer.sourceforge.net
>>>>>
>>>>>16 Jun 2003 - Version 0.5.25
>>>>>--------------------------
>>>>>[-] Bug with LDC/LDC_W in BCEL fixed. I hope, that this is reason, why
>>>>> JVM throws "VerifyError: Illegal constant pool index".
>>>>>[+] Now you can use doubleclick in Packages/Classes/Methods views to
>>>>> open method in editor. Context menu was not very convinient way.
>>>>>[+] "Live" thread call graph. Now it refreshes automatically, as any other
>>>>> profiler view. "Refresh" button removed.
>>>>>[+] New filters for thread call graph. You can set, that you want to
>>>>> see control flows with at least 1% of total time, or 2%, 3%, 5%, 10%.
>>>>> This allows remove most of not interesting details like methods,
>>>>> which were called only once, or don't use much time.
>>>>>[+] "Pause CPU profiling on method leave" option in launch configuration
>>>>> dialog. When it is on, profiler will stop gathering statistics and
>>>>> resume when control flow will enter in this method again. This allows
>>>>> you profile only part of application, without parts, which do other
>>>>> things, like preparing data for interesting part.
>>>>>[-] Fixed crash in ProfilerDLL during heap profiling. Does anybody knows
>>>>> why OptimizeIt is 2 times faster when does heap profiling? It seems, that
>>>>> most slow part is getting allocation trace, and it is in JVM. I don't
>>>>> know, how to make it faster. :-(
>>>>>
>>>>>
>>>
>>>
>>>
>
>
>
|
|
|
| Re: [ANN] Eclipse profiler plugin, 0.5.25 [message #75465 is a reply to message #75072] |
Mon, 16 June 2003 13:51 |
| Eclipse User |
|
|
|
Originally posted by: sddg.yahoo.com
Is there a way to profile remote j9 applications?
If yes, with what options should the j9 vm be started?
"Konstantin Scheglov" <scheglov_ke@nlmk.ru> wrote in message
news:Nxz%23G77MDHA.1676@fairy.ao.nlmk...
>
> http://eclipsecolorer.sourceforge.net
>
> 16 Jun 2003 - Version 0.5.25
> --------------------------
> [-] Bug with LDC/LDC_W in BCEL fixed. I hope, that this is reason, why
> JVM throws "VerifyError: Illegal constant pool index".
> [+] Now you can use doubleclick in Packages/Classes/Methods views to
> open method in editor. Context menu was not very convinient way.
> [+] "Live" thread call graph. Now it refreshes automatically, as any other
> profiler view. "Refresh" button removed.
> [+] New filters for thread call graph. You can set, that you want to
> see control flows with at least 1% of total time, or 2%, 3%, 5%, 10%.
> This allows remove most of not interesting details like methods,
> which were called only once, or don't use much time.
> [+] "Pause CPU profiling on method leave" option in launch configuration
> dialog. When it is on, profiler will stop gathering statistics and
> resume when control flow will enter in this method again. This allows
> you profile only part of application, without parts, which do other
> things, like preparing data for interesting part.
> [-] Fixed crash in ProfilerDLL during heap profiling. Does anybody knows
> why OptimizeIt is 2 times faster when does heap profiling? It seems,
that
> most slow part is getting allocation trace, and it is in JVM. I don't
> know, how to make it faster. :-(
>
>
> --
> SY, Konstantin.
|
|
|
| Re: [ANN] Eclipse profiler plugin, 0.5.25 [message #75482 is a reply to message #75342] |
Mon, 16 June 2003 13:48 |
| Eclipse User |
|
|
|
Originally posted by: scheglov_ke.nlmk.ru
Christian Sell <cse@dynabean.de> wrote:
>> I mean start in Eclipse.
> not possible under Linux, right?
Possible.
At least previous version was tested that it works under
Linux inside of Eclipse.
>>
>>
>>>> In you case you should add:
>>>> -D__PROFILER_WAIT_FRONTEND_CONNECT=1
>>>> (it is 0 by default, i.e. allow application to run, even
>>>>there is no frontend connected).
>>>
>>>is there documentation anywhere on the recognized options?
>>
>> No.
>>
>>
>>
>>>thanks,
>>>Christian
>>
>>
>>>>
>>>>>I already posted this on the mailing list.. I am missing an option to
>>>>>pause the program being profiled remotely until the profiler connects to
>>>>>it. This is important for standalone programs (i.e., non-appserver)
>>>>>which otherwise may just run through from start to stop. Unfortunately,
>>>>>under Linux I can only use the remote profiler.
>>>>
>>>>
>>>>>thanks,
>>>>>Christian
>>>>
>>>>
>>>>>Konstantin Scheglov wrote:
>>>>>
>>>>>
>>>>>>http://eclipsecolorer.sourceforge.net
>>>>>>
>>>>>>16 Jun 2003 - Version 0.5.25
>>>>>>--------------------------
>>>>>>[-] Bug with LDC/LDC_W in BCEL fixed. I hope, that this is reason, why
>>>>>> JVM throws "VerifyError: Illegal constant pool index".
>>>>>>[+] Now you can use doubleclick in Packages/Classes/Methods views to
>>>>>> open method in editor. Context menu was not very convinient way.
>>>>>>[+] "Live" thread call graph. Now it refreshes automatically, as any other
>>>>>> profiler view. "Refresh" button removed.
>>>>>>[+] New filters for thread call graph. You can set, that you want to
>>>>>> see control flows with at least 1% of total time, or 2%, 3%, 5%, 10%.
>>>>>> This allows remove most of not interesting details like methods,
>>>>>> which were called only once, or don't use much time.
>>>>>>[+] "Pause CPU profiling on method leave" option in launch configuration
>>>>>> dialog. When it is on, profiler will stop gathering statistics and
>>>>>> resume when control flow will enter in this method again. This allows
>>>>>> you profile only part of application, without parts, which do other
>>>>>> things, like preparing data for interesting part.
>>>>>>[-] Fixed crash in ProfilerDLL during heap profiling. Does anybody knows
>>>>>> why OptimizeIt is 2 times faster when does heap profiling? It seems, that
>>>>>> most slow part is getting allocation trace, and it is in JVM. I don't
>>>>>> know, how to make it faster. :-(
>>>>>>
>>>>>>
>>>>
>>>>
>>>>
>>
>>
>>
--
SY, Konstantin.
|
|
|
| Re: [ANN] Eclipse profiler plugin, 0.5.25 [message #75515 is a reply to message #75482] |
Mon, 16 June 2003 14:28 |
Christian Sell
Messages: 77
Registered: July 2009 |
Member |
|
|
Konstantin Scheglov wrote:
> Christian Sell <cse@dynabean.de> wrote:
>
>
>>> I mean start in Eclipse.
>>
>>not possible under Linux, right?
>
> Possible.
> At least previous version was tested that it works under
ok, so the statement below quoted from the online docs is wrong:
Linux installation
For Linux only remote profiling supported now.
> Linux inside of Eclipse.
>
>
>
>>>
>>>>> In you case you should add:
>>>>> -D__PROFILER_WAIT_FRONTEND_CONNECT=1
>>>>> (it is 0 by default, i.e. allow application to run, even
>>>>>there is no frontend connected).
>>>>
>>>>is there documentation anywhere on the recognized options?
>>>
>>> No.
>>>
>>>
>>>
>>>
>>>>thanks,
>>>>Christian
>>>
>>>
>>>>>>I already posted this on the mailing list.. I am missing an option to
>>>>>>pause the program being profiled remotely until the profiler connects to
>>>>>>it. This is important for standalone programs (i.e., non-appserver)
>>>>>>which otherwise may just run through from start to stop. Unfortunately,
>>>>>>under Linux I can only use the remote profiler.
>>>>>
>>>>>
>>>>>>thanks,
>>>>>>Christian
>>>>>
>>>>>
>>>>>>Konstantin Scheglov wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>>http://eclipsecolorer.sourceforge.net
>>>>>>>
>>>>>>>16 Jun 2003 - Version 0.5.25
>>>>>>>--------------------------
>>>>>>>[-] Bug with LDC/LDC_W in BCEL fixed. I hope, that this is reason, why
>>>>>>> JVM throws "VerifyError: Illegal constant pool index".
>>>>>>>[+] Now you can use doubleclick in Packages/Classes/Methods views to
>>>>>>> open method in editor. Context menu was not very convinient way.
>>>>>>>[+] "Live" thread call graph. Now it refreshes automatically, as any other
>>>>>>> profiler view. "Refresh" button removed.
>>>>>>>[+] New filters for thread call graph. You can set, that you want to
>>>>>>> see control flows with at least 1% of total time, or 2%, 3%, 5%, 10%.
>>>>>>> This allows remove most of not interesting details like methods,
>>>>>>> which were called only once, or don't use much time.
>>>>>>>[+] "Pause CPU profiling on method leave" option in launch configuration
>>>>>>> dialog. When it is on, profiler will stop gathering statistics and
>>>>>>> resume when control flow will enter in this method again. This allows
>>>>>>> you profile only part of application, without parts, which do other
>>>>>>> things, like preparing data for interesting part.
>>>>>>>[-] Fixed crash in ProfilerDLL during heap profiling. Does anybody knows
>>>>>>> why OptimizeIt is 2 times faster when does heap profiling? It seems, that
>>>>>>> most slow part is getting allocation trace, and it is in JVM. I don't
>>>>>>> know, how to make it faster. :-(
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>>
>
>
|
|
|
| Re: [ANN] Eclipse profiler plugin, 0.5.25 [message #75926 is a reply to message #75515] |
Tue, 17 June 2003 03:12 |
| Eclipse User |
|
|
|
Originally posted by: scheglov_ke.nlmk.ru
Christian Sell <cse@dynabean.de> wrote:
>> At least previous version was tested that it works under
> ok, so the statement below quoted from the online docs is wrong:
> Linux installation
> For Linux only remote profiling supported now.
Ok, agree.
Thanks, documentation changed.
--
SY, Konstantin.
|
|
|
| Re: [ANN] Eclipse profiler plugin, 0.5.25 [message #75985 is a reply to message #75465] |
Tue, 17 June 2003 04:38 |
| Eclipse User |
|
|
|
Originally posted by: scheglov_ke.nlmk.ru
Sui Ma <sddg@yahoo.com> wrote:
> Is there a way to profile remote j9 applications?
> If yes, with what options should the j9 vm be started?
I just downloaded WSDD and try to start test application.
(without profiling)
From IDE - no problem, it starts.
But when I try to execute same command from command line,
I receive following:
C:\eclipsePL\workspace\ru.nlmk.eclipse.plugins.profiler\nati ve\ProfilerDLL >"C:\Program Files\IBM\Device Developer\wsdd5.
0\ive\bin\j9" -classpath "C:\Program Files\IBM\Device Developer\workspace\tets" -jcl:foun Test
Fatal error: Unable to find and initialize required class java/lang/Object
Do you know, where is problem?
> "Konstantin Scheglov" <scheglov_ke@nlmk.ru> wrote in message
> news:Nxz%23G77MDHA.1676@fairy.ao.nlmk...
>>
>> http://eclipsecolorer.sourceforge.net
>>
>> 16 Jun 2003 - Version 0.5.25
>> --------------------------
>> [-] Bug with LDC/LDC_W in BCEL fixed. I hope, that this is reason, why
>> JVM throws "VerifyError: Illegal constant pool index".
>> [+] Now you can use doubleclick in Packages/Classes/Methods views to
>> open method in editor. Context menu was not very convinient way.
>> [+] "Live" thread call graph. Now it refreshes automatically, as any other
>> profiler view. "Refresh" button removed.
>> [+] New filters for thread call graph. You can set, that you want to
>> see control flows with at least 1% of total time, or 2%, 3%, 5%, 10%.
>> This allows remove most of not interesting details like methods,
>> which were called only once, or don't use much time.
>> [+] "Pause CPU profiling on method leave" option in launch configuration
>> dialog. When it is on, profiler will stop gathering statistics and
>> resume when control flow will enter in this method again. This allows
>> you profile only part of application, without parts, which do other
>> things, like preparing data for interesting part.
>> [-] Fixed crash in ProfilerDLL during heap profiling. Does anybody knows
>> why OptimizeIt is 2 times faster when does heap profiling? It seems,
> that
>> most slow part is getting allocation trace, and it is in JVM. I don't
>> know, how to make it faster. :-(
>>
>>
>> --
>> SY, Konstantin.
--
SY, Konstantin.
|
|
|
| Re: [ANN] Eclipse profiler plugin, 0.5.25 [message #75994 is a reply to message #75465] |
Tue, 17 June 2003 05:22 |
| Eclipse User |
|
|
|
Originally posted by: scheglov_ke.nlmk.ru
Sui Ma <sddg@yahoo.com> wrote:
> Is there a way to profile remote j9 applications?
I tryed to start application with JVMPI and have same problem
as with IBM JDK - it crashes during loading instrumentation classes
(Trace and BCEL classes). I don't know what to do with this. For
SUN JDK this works on Windows, Linux and Solaris (AFAIK).
> If yes, with what options should the j9 vm be started?
> "Konstantin Scheglov" <scheglov_ke@nlmk.ru> wrote in message
> news:Nxz%23G77MDHA.1676@fairy.ao.nlmk...
>>
>> http://eclipsecolorer.sourceforge.net
>>
>> 16 Jun 2003 - Version 0.5.25
>> --------------------------
>> [-] Bug with LDC/LDC_W in BCEL fixed. I hope, that this is reason, why
>> JVM throws "VerifyError: Illegal constant pool index".
>> [+] Now you can use doubleclick in Packages/Classes/Methods views to
>> open method in editor. Context menu was not very convinient way.
>> [+] "Live" thread call graph. Now it refreshes automatically, as any other
>> profiler view. "Refresh" button removed.
>> [+] New filters for thread call graph. You can set, that you want to
>> see control flows with at least 1% of total time, or 2%, 3%, 5%, 10%.
>> This allows remove most of not interesting details like methods,
>> which were called only once, or don't use much time.
>> [+] "Pause CPU profiling on method leave" option in launch configuration
>> dialog. When it is on, profiler will stop gathering statistics and
>> resume when control flow will enter in this method again. This allows
>> you profile only part of application, without parts, which do other
>> things, like preparing data for interesting part.
>> [-] Fixed crash in ProfilerDLL during heap profiling. Does anybody knows
>> why OptimizeIt is 2 times faster when does heap profiling? It seems,
> that
>> most slow part is getting allocation trace, and it is in JVM. I don't
>> know, how to make it faster. :-(
>>
>>
>> --
>> SY, Konstantin.
--
SY, Konstantin.
|
|
|
| Re: [ANN] Eclipse profiler plugin, 0.5.25 [message #76297 is a reply to message #75985] |
Tue, 17 June 2003 13:49 |
| Eclipse User |
|
|
|
Originally posted by: sddg.yahoo.com
Here is how you start a typical j9 vm:
C:\Program Files\IBM\Device
Developer\wsdd5.0\ive\bin\j9 -Xbootclasspath:C:\Program Files\IBM\Device
Developer\wsdd5.0\ive\runtimes\common\ive\lib\jclFoundation\ classes.zip;C:\P
rogram Files\IBM\Device
Developer\wsdd5.0\ive\runtimes\common\ive\lib\jclFoundation\ locale.zip;C:\Pr
ogram Files\IBM\Device
Developer\wsdd5.0\ive\runtimes\common\ive\lib\charconv.zip -classpath
d:\develop\oscar\bin;\\Dotnetserver\Oscar\osgi.jar -jcl:foun
org.ungoverned.oscar.Main
so bootclasspath must contain the j9 core classes, classpath - the classes
of the application
in this case -jcl:foun might not be required but I include it anyway
|
|
|
| Re: [ANN] Eclipse profiler plugin, 0.5.25 [message #77310 is a reply to message #76297] |
Wed, 18 June 2003 05:20 |
| Eclipse User |
|
|
|
Originally posted by: scheglov_ke.nlmk.ru
Sui Ma <sddg@yahoo.com> wrote:
As you can see in my other post, now I can start application with j9,
but class instrumentation does not work.
> Here is how you start a typical j9 vm:
> C:\Program Files\IBM\Device
> Developer\wsdd5.0\ive\bin\j9 -Xbootclasspath:C:\Program Files\IBM\Device
> Developer\wsdd5.0\ive\runtimes\common\ive\lib\jclFoundation\ classes.zip;C:\P
> rogram Files\IBM\Device
> Developer\wsdd5.0\ive\runtimes\common\ive\lib\jclFoundation\ locale.zip;C:\Pr
> ogram Files\IBM\Device
> Developer\wsdd5.0\ive\runtimes\common\ive\lib\charconv.zip -classpath
> d:\develop\oscar\bin;\\Dotnetserver\Oscar\osgi.jar -jcl:foun
> org.ungoverned.oscar.Main
> so bootclasspath must contain the j9 core classes, classpath - the classes
> of the application
> in this case -jcl:foun might not be required but I include it anyway
--
SY, Konstantin.
|
|
|
| Re: [ANN] Eclipse profiler plugin, 0.5.25 [message #77763 is a reply to message #77310] |
Wed, 18 June 2003 15:13 |
| Eclipse User |
|
|
|
Originally posted by: sddg.yahoo.com
that's a pity :(
such a fine profiler
Heap profiling, though might be a bit more powerful:
1. showing each instance object's owner
"Konstantin Scheglov" <scheglov_ke@nlmk.ru> wrote in message
news:mI6IhlVNDHA.3980@fairy.ao.nlmk...
> Sui Ma <sddg@yahoo.com> wrote:
>
> As you can see in my other post, now I can start application with j9,
> but class instrumentation does not work.
>
> > Here is how you start a typical j9 vm:
>
> > C:\Program Files\IBM\Device
> > Developer\wsdd5.0\ive\bin\j9 -Xbootclasspath:C:\Program Files\IBM\Device
> >
Developer\wsdd5.0\ive\runtimes\common\ive\lib\jclFoundation\ classes.zip;C:\P
> > rogram Files\IBM\Device
> >
Developer\wsdd5.0\ive\runtimes\common\ive\lib\jclFoundation\ locale.zip;C:\Pr
> > ogram Files\IBM\Device
> > Developer\wsdd5.0\ive\runtimes\common\ive\lib\charconv.zip -classpath
> > d:\develop\oscar\bin;\\Dotnetserver\Oscar\osgi.jar -jcl:foun
> > org.ungoverned.oscar.Main
>
>
>
> > so bootclasspath must contain the j9 core classes, classpath - the
classes
> > of the application
>
> > in this case -jcl:foun might not be required but I include it anyway
>
>
>
> --
> SY, Konstantin.
|
|
|
Goto Forum:
Current Time: Sat Nov 09 03:50:30 GMT 2024
Powered by FUDForum. Page generated in 0.04410 seconds |
] 
Search
Help
Register
Login
Home
