Home » Archived » Test and Performance Tools Platform (TPTP) » Documentation on probes and otehr features?
|
| Re: Documentation on probes and otehr features? [message #57361 is a reply to message #56982] |
Fri, 10 March 2006 16:35   |
Eclipse User |
|
|
|
Originally posted by: Navid_Mehregani_nmehrega.ca.ibm.com
This is a multipart message in MIME format.
--=_alternative 005B0D8C8525712D_=
Content-Type: text/plain; charset="US-ASCII"
>Since the online help of TPTP does not work (see my other thread) I have
>a few questions:
I've addressed your problem about the help content of TPTP. Please see
the thread where you posted the question.
>I would like to profile not my entire application but rather start & stop
>at specific points during execution (i.e. I want to analyze just a
>particular workhorse method after reading some configuration file and
>before writing the result). Can that be done?
>In the profile wizard there is a feature "probes" mentioned. What is
>this and what can it be used for?
Yes, you can definitely control the profiler from your application. Please
see the following documentation:
http://www.eclipse.org/tptp/home/downloads/installguide/Agen tController41.html
click on the platform that you're profiling on and scroll down to the "
Invocation of the Java Profiler from the Command Line" section. You
should look into starting the profiler Agent in "applicationControlled"
mode. Once the profiler agent is started in this mode, you can control it
via the Profiler class.
Probekit is a tool in TPTP that allows you to instrument your application
for the purpose of collecting detailed runtime information about a
program's object, methods, instance variables, arguments, and exceptions.
Please see the following document in the help content for more details:
"Monitoring and analyzing performance" -> "Collecting run-time data with
user-defined probes". You can use probekit to write probes that will
activate/deactivate profiling when desired then run your application in
"applicationControlled" mode and have your probes control the profiler.
Note that TPTP 4.1 currently gets shipped with static probekit, which
requires you to instrument your applications "manually". TPTP 4.2 will
include dynamic probekit which allows you to apply your probes on-the-fly.
The instrumentation will be done in memory and there will be no clean-up
work required, since the .class files are not modified and the
insturmentation is done in memory.
Navid Mehregani
--=_alternative 005B0D8C8525712D_=
Content-Type: text/html; charset="US-ASCII"
<br><font size=2><tt>>Since the online help of TPTP does not work (see
my other thread) I have <br>
>a few questions:</tt></font>
<br>
<br><font size=2 face="sans-serif">I've addressed your problem about the
help content of TPTP. Please see the thread where you posted the
question.</font>
<br>
<br><font size=2><tt><br>
>I would like to profile not my entire application but rather start
& stop <br>
>at specific points during execution (i.e. I want to analyze just a
<br>
>particular workhorse method after reading some configuration file and
<br>
>before writing the result). Can that be done?</tt></font>
<br><font size=2><tt>>In the profile wizard there is a feature "probes"
mentioned. What is <br>
>this and what can it be used for?</tt></font>
<br>
<br><font size=2 face="sans-serif">Yes, you can definitely control the
profiler from your application. Please see the following documentation:
http://www.eclipse.org/tptp/home/downloads/installguide/Agen tController41.html</font>
<br><font size=2 face="sans-serif">click on the platform that you're profiling
on and scroll down to the "Invocation of the Java Profiler from the
Command Line" section. You should look into starting the profiler
Agent in "applicationControlled" mode. Once the profiler
agent is started in this mode, you can control it via the Profiler class.</font>
<br><font size=2 face="sans-serif"><br>
Probekit is a tool in TPTP that allows you to instrument your application
for the purpose of collecting detailed runtime information about a program's
object, methods, instance variables, arguments, and exceptions. Please
see the following document in the help content for more details: "Monitoring
and analyzing performance" -> "Collecting run-time data with
user-defined probes". You can use probekit to write probes that
will activate/deactivate profiling when desired then run your application
in "applicationControlled" mode and have your probes control
the profiler.</font>
<br>
<br><font size=2 face="sans-serif">Note that TPTP 4.1 currently gets shipped
with static probekit, which requires you to instrument your applications
"manually". TPTP 4.2 will include dynamic probekit which
allows you to apply your probes on-the-fly. The instrumentation will
be done in memory and there will be no clean-up work required, since the
class files are not modified and the insturmentation is done in memory.</font>
<br>
<br><font size=2 face="sans-serif">Navid Mehregani</font>
--=_alternative 005B0D8C8525712D_=--
|
|
|
| Re: Documentation on probes and otehr features? [message #57461 is a reply to message #57361] |
Fri, 10 March 2006 22:26 |
 Michael Moser
Messages: 914
Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0016_01C6449A.03EB4340
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Thanks Navid,
that sounds very promising. I'll have a closer look.
Michael
<Navid_Mehregani_nmehrega@ca.ibm.com> wrote in message =
news:dus9s3$irg$1@utils.eclipse.org...
>Since the online help of TPTP does not work (see my other thread) I =
have=20
>a few questions:=20
I've addressed your problem about the help content of TPTP. Please see =
the thread where you posted the question.=20
>I would like to profile not my entire application but rather start & =
stop=20
>at specific points during execution (i.e. I want to analyze just a=20
>particular workhorse method after reading some configuration file and=20
>before writing the result). Can that be done?=20
>In the profile wizard there is a feature "probes" mentioned. What is=20
>this and what can it be used for?=20
Yes, you can definitely control the profiler from your application. =
Please see the following documentation: =
http://www.eclipse.org/tptp/home/downloads/installguide/Agen tController41=
..html=20
click on the platform that you're profiling on and scroll down to the =
"Invocation of the Java Profiler from the Command Line" section. You =
should look into starting the profiler Agent in "applicationControlled" =
mode. Once the profiler agent is started in this mode, you can control =
it via the Profiler class.=20
Probekit is a tool in TPTP that allows you to instrument your =
application for the purpose of collecting detailed runtime information =
about a program's object, methods, instance variables, arguments, and =
exceptions. Please see the following document in the help content for =
more details: "Monitoring and analyzing performance" -> "Collecting =
run-time data with user-defined probes". You can use probekit to write =
probes that will activate/deactivate profiling when desired then run =
your application in "applicationControlled" mode and have your probes =
control the profiler.=20
Note that TPTP 4.1 currently gets shipped with static probekit, which =
requires you to instrument your applications "manually". TPTP 4.2 will =
include dynamic probekit which allows you to apply your probes =
on-the-fly. The instrumentation will be done in memory and there will =
be no clean-up work required, since the class files are not modified and =
the insturmentation is done in memory.=20
Navid Mehregani
------=_NextPart_000_0016_01C6449A.03EB4340
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2802" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Thanks Navid,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>that sounds very promising. I'll have a =
closer=20
look.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Michael</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><<A=20
href=3D"mailto:Navid_Mehregani_nmehrega@ca.ibm.com">Navid_Mehregani_nmehr=
ega@ca.ibm.com</A>>=20
wrote in message <A=20
href=3D"news:dus9s3$irg$1@utils.eclipse.org">news:dus9s3$irg$1@utils.ecli=
pse.org</A>...</DIV><BR><FONT=20
size=3D2><TT>>Since the online help of TPTP does not work (see my =
other thread)=20
I have <BR>>a few questions:</TT></FONT> <BR><BR><FONT =
face=3Dsans-serif=20
size=3D2>I've addressed your problem about the help content of TPTP. =
Please=20
see the thread where you posted the question.</FONT> <BR><BR><FONT=20
size=3D2><TT><BR>>I would like to profile not my entire application =
but rather=20
start & stop <BR>>at specific points during execution (i.e. I =
want to=20
analyze just a <BR>>particular workhorse method after reading some=20
configuration file and <BR>>before writing the result). Can that be=20
done?</TT></FONT> <BR><FONT size=3D2><TT>>In the profile wizard there =
is a=20
feature "probes" mentioned. What is <BR>>this and what can it be used =
for?</TT></FONT> <BR><BR><FONT face=3Dsans-serif size=3D2>Yes, you can =
definitely=20
control the profiler from your application. Please see the =
following=20
documentation:=20
http://www.eclipse.org/tptp/home/downloads/installguide/Agen tController41=
..html</FONT>=20
<BR><FONT face=3Dsans-serif size=3D2>click on the platform that you're =
profiling on=20
and scroll down to the "Invocation of the Java Profiler from the Command =
Line"=20
section. You should look into starting the profiler Agent in=20
"applicationControlled" mode. Once the profiler agent is started =
in this=20
mode, you can control it via the Profiler class.</FONT> <BR><FONT=20
face=3Dsans-serif size=3D2><BR>Probekit is a tool in TPTP that allows =
you to=20
instrument your application for the purpose of collecting detailed =
runtime=20
information about a program's object, methods, instance variables, =
arguments,=20
and exceptions. Please see the following document in the help =
content for=20
more details: "Monitoring and analyzing performance" -> "Collecting =
run-time=20
data with user-defined probes". You can use probekit to write =
probes that=20
will activate/deactivate profiling when desired then run your =
application in=20
"applicationControlled" mode and have your probes control the =
profiler.</FONT>=20
<BR><BR><FONT face=3Dsans-serif size=3D2>Note that TPTP 4.1 currently =
gets shipped=20
with static probekit, which requires you to instrument your applications =
"manually". TPTP 4.2 will include dynamic probekit which allows =
you to=20
apply your probes on-the-fly. The instrumentation will be done in =
memory=20
and there will be no clean-up work required, since the class files are =
not=20
modified and the insturmentation is done in memory.</FONT> <BR><BR><FONT =
face=3Dsans-serif size=3D2>Navid Mehregani</FONT></BODY></HTML>
------=_NextPart_000_0016_01C6449A.03EB4340--
|
|
| | |
| Re: Documentation on probes and other features? [message #58026 is a reply to message #57860] |
Tue, 14 March 2006 15:08 |
Michael Moser
Messages: 914
Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_001C_01C64781.9104EC10
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sorry that I keep coming back to this but, alas, the documentation is =
rather terse on this - at least I don't consider this self-explanatory =
at all!
As you may recall, I want to do application controlled profiling, i.e. I =
want to measure just a specific part of my application.
So I create a Profiler=20
profiler =3D Profiler.getProfiler();
System.out.println("TPTP Profiler: " + profiler);
and issue:
profiler.startProfiling(true); =20
profiler.markHeap(); =20
before the code that I want to analyze and
profiler.analyzeHeap("profile-run" + i);
profiler.stopProfiling();
after that code. Is this correct?
I also managed to start my application in "applicationControlled" mode =
by adding
-XrunpiAgent:server=3Dapplication=20
to the VM arguments. That seems to run as well, at least the =
System.out.println(profiler) shows that I got a "profiler".
But in contrast to the automatic profiling (where after each profiling =
automatically a new entry appears under the performance profiling =
project name listed on the Profiling... =3D> Destination tab) nothing =
else seems to happens. Wht do I need to do for the actual profiling? Am =
I correct, that I have to run this now with the "normal" Run... instead =
of Profiling...? Because if I run this with Profiling... the VM crashes =
in the moment when the application wants to obtain the Profiler.
And where do the profiling data go??? I searched my entire disk for a =
file called "profile-run*" but found nothing...
Michael
------=_NextPart_000_001C_01C64781.9104EC10
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2802" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Sorry that I keep coming back to this =
but, alas,=20
the documentation is rather terse on this - at least I don't =
consider this=20
self-explanatory at all!</FONT></DIV>
<DIV>
<DIV><FONT face=3Dsans-serif size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>As you may recall, I want to do =
application=20
controlled profiling, i.e. I want to measure just a specific part of my=20
application.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3Dsans-serif size=3D2>So I create a Profiler =
</FONT></DIV>
<DIV><FONT face=3Dsans-serif size=3D2></FONT> </DIV>
<DIV><FONT face=3Dsans-serif=20
size=3D2> &nbs=
p; profiler=20
=3D=20
Profiler.getProfiler();<BR> &nbs=
p; &nbs p; System.out.println( "TPTP=20
Profiler: " + profiler);<BR></FONT></DIV>
<DIV><FONT face=3Dsans-serif size=3D2>and </FONT><FONT =
face=3Dsans-serif=20
size=3D2>issue:</FONT></DIV>
<DIV><FONT face=3Dsans-serif size=3D2></FONT> </DIV>
<DIV><FONT face=3Dsans-serif=20
size=3D2> &nbs=
p; profiler.startProf iling(true);  =
;   ;   ;=
<BR> &nb=
sp; profile r.markHeap(); &n=
bsp; &n bsp; <BR></FON=
T></DIV>
<DIV><FONT face=3Dsans-serif size=3D2>before the code that I =
want to=20
analyze </FONT><FONT face=3Dsans-serif size=3D2>and</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial=20
size=3D2> &nbs=
p; profiler.analyzeHe ap( "profile-run"=20
+=20
i);<BR> =
profiler.stopProfili ng(); <BR></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>after that code. Is this =
correct?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV></DIV>
<DIV><FONT face=3Dsans-serif size=3D2>I also managed to start my =
application in=20
"applicationControlled" mode by adding</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2> =
-XrunpiAgent:server=3Dapplication=20
</FONT></DIV>
<DIV><FONT face=3Dsans-serif size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>to the VM arguments. That seems to run =
as well, at=20
least the System.out.println(profiler) shows that I got a=20
"profiler".</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>But in contrast to the automatic =
profiling (where=20
after each profiling automatically a new entry appears under the=20
performance profiling project name listed on =
the Profiling... =3D>=20
Destination tab) nothing else seems to happens. Wht do I need =
to do=20
for the actual profiling? </FONT><FONT face=3DArial size=3D2>Am I =
correct, that I=20
have to run this now with the "normal" Run... instead of =
Profiling...?=20
Because if I run this with Profiling... the VM crashes in the moment =
when the=20
application wants to obtain the Profiler.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>And where do the profiling data go??? I =
searched my=20
entire disk for a file called "profile-run*" but found =
nothing...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Michael</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV></BODY></HTML>
------=_NextPart_000_001C_01C64781.9104EC10--
|
|
|
| Re: Controlling the profiler programmatically [message #58272 is a reply to message #58026] |
Wed, 15 March 2006 00:02 |
| Eclipse User |
|
|
|
Originally posted by: Navid_Mehregani_nmehrega.ca.ibm.com
--=_mixed 0000058A85257132_=
Content-Type: multipart/alternative; boundary="=_alternative 0000058A85257132_="
--=_alternative 0000058A85257132_=
Content-Type: text/plain; charset="US-ASCII"
*Changed the subject to match our discussion*
>Sorry that I keep coming back to this but, alas, the documentation is
rather terse on this - at least I don't consider this self-explanatory at
all!
I agree that the documentation on this is minimal. If you think we need
better documentation on this subject, I urge you to open an enhancement
request here https://bugs.eclipse.org/bugs/enter_bug.cgi?product=TPTP for
creating a document that explains (with examples) on how you can control
the profiler programmatically. Please add me to the CC list of your
enhancement (nmehrega@ca.ibm.com)
I'm attaching a simple example that controls the profiler
programmatically. Please take a look at it to see how the APIs should be
used.
>I also managed to start my application in "applicationControlled" mode by
adding
>
> -XrunpiAgent:server=application
Is this a typo? It should really be
-XrunpiAgent:server=applicationControlled not
-XrunpiAgent:server=application.
>But in contrast to the automatic profiling (where after each profiling
automatically a new entry appears under the performance profiling project
name listed on the Profiling... => Destination tab) nothing else seems to
happens.
> Wht do I need to do for the actual profiling? Am I correct, that I have
to run this now with the "normal" Run... instead of Profiling...? Because
if I run this with Profiling... the VM crashes in the moment when the
application
> wants to obtain the Profiler.
>
>And where do the profiling data go??? I searched my entire disk for a
file called "profile-run*" but found nothing...
Yes, you're just suppose to "Run" this and not profile it. In terms of
where the data goes.. I think you missed this part of the instructions:
The pluginconfig.xml file must be modified to use this mode. The
pluginconfig.xml is located in the following directory:
<agent_controller_home>\plugins\org.eclipse.tptp.platform.collection.framework_ <version>\config\pluginconfig.xml
The following modification is required:
<Agent client="DYNAMIC" configuration="default" dataChannelSize="64M"
name="Java Profiling Agent" type="Profiler"/>
should be modified to
<Agent client="HEADLESS" configuration="default" dataChannelSize="64M"
name="Java Profiling Agent" type="Profiler" logFile="C:\profile.trcxml"/>
Note that the Agent client attribute has been changed to "HEADLESS" and
that the "logFile" attribute has been added.
The profiling data will be sent to the file specified in the value of
'logFile'. In the above example, it's C:\profile.trcxml. You then have
to import this file into the workbench by right clicking in the profiling
monitor view and selecting import -> expand profile and logging folder ->
select profiling file -> next -> specify your profiling file -> select the
amount of data you want to display in the range tab (i.e. show heap
statistics, show execution statistics, or show full data) -> finish.
I completely agree that the documentation on this should be improved,
which is why I've asked you to open an enhancement request.
--=_alternative 0000058A85257132_=
Content-Type: text/html; charset="US-ASCII"
<br><font size=2 face="sans-serif">*Changed the subject to match our discussion*</font>
<br>
<br><font size=2 face="Arial">>Sorry that I keep coming back to this
but, alas, the documentation is rather terse on this - at least I don't
consider this self-explanatory at all!</font>
<br>
<br><font size=2 face="Arial">I agree that the documentation on this is
minimal. If you think we need better documentation on this subject,
I urge you to open an enhancement request here https://bugs.eclipse.org/bugs/enter_bug.cgi?product=TPTP
for creating a document that explains (with examples) on how you can control
the profiler programmatically. Please add me to the CC list of your
enhancement (nmehrega@ca.ibm.com)</font>
<br>
<br><font size=2 face="Arial">I'm attaching a simple example that controls
the profiler programmatically. Please take a look at it to see how
the APIs should be used.</font>
<br>
<br><font size=2 face="sans-serif">>I also managed to start my application
in "applicationControlled" mode by adding</font>
<br><font size=3>> </font>
<br><font size=2 face="Arial">> -XrunpiAgent:server=application
</font>
<br>
<br><font size=2 face="Arial">Is this a typo? It should really be
-XrunpiAgent:server=applicationControlled not -XrunpiAgent:server=application.</font>
<br>
<br><font size=2 face="Arial">>But in contrast to the automatic profiling
(where after each profiling automatically a new entry appears under the
performance profiling project name listed on the Profiling... => Destination
tab) nothing else seems to happens. </font>
<br><font size=2 face="Arial">> Wht do I need to do for the actual profiling?
Am I correct, that I have to run this now with the "normal" Run...
instead of Profiling...? Because if I run this with Profiling... the VM
crashes in the moment when the application </font>
<br><font size=2 face="Arial">> wants to obtain the Profiler.</font>
<br><font size=3>> </font>
<br><font size=2 face="Arial">>And where do the profiling data go???
I searched my entire disk for a file called "profile-run*" but
found nothing...</font>
<br>
<br><font size=2 face="Arial">Yes, you're just suppose to "Run"
this and not profile it. In terms of where the data goes.. I think
you missed this part of the instructions:</font>
<br>
<br><font size=2 face="Arial">The pluginconfig.xml file must be modified
to use this mode. The pluginconfig.xml is located in the following directory:
</font>
<br><font size=2 face="Arial"> <agent_controller_home>\plugins\org.eclipse.tp tp.platform.collection.framework_<version>\con fig\pluginconfig.xml </font>
<br>
<br><font size=2 face="Arial">The following modification is required: </font>
<br><font size=2 face="Arial"><Agent client="DYNAMIC" configuration="default"
dataChannelSize="64M" name="Java Profiling Agent" type="Profiler"/></font>
<br>
<br><font size=2 face="Arial">should be modified to </font>
<br>
<br><font size=2 face="Arial"><Agent client="HEADLESS" configuration="default"
dataChannelSize="64M" name="Java Profiling Agent" type="Profiler"
logFile="C:\profile.trcxml"/></font >
<br>
<br><font size=2 face="Arial">Note that the Agent client attribute has
been changed to "HEADLESS" and that the "logFile" attribute
has been added. </font>
<br>
<br><font size=2 face="Arial">The profiling data will be sent to the file
specified in the value of 'logFile'. In the above example, it's C:\profile.trcxml.
You then have to import this file into the workbench by right clicking
in the profiling monitor view and selecting import -> expand profile
and logging folder -> select profiling file -> next -> specify
your profiling file -> select the amount of data you want to display
in the range tab (i.e. show heap statistics, show execution statistics,
or show full data) -> finish.</font>
<br>
<br><font size=2 face="Arial">I completely agree that the documentation
on this should be improved, which is why I've asked you to open an enhancement
request.</font>
<br>
<br>
<br><font size=2 face="Arial"> </font>
--=_alternative 0000058A85257132_=--
--=_mixed 0000058A85257132_=
Content-Type: application/octet-stream; name="Testpi.java"
Content-Disposition: attachment; filename="Testpi.java"
Content-Transfer-Encoding: base64
aW1wb3J0IG9yZy5lY2xpcHNlLmh5YWRlcy5jb2xsZWN0aW9uLnByb2ZpbGVy LlByb2ZpbGVyOw0K
DQovKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioq
KioqKioqKioqKioqKioqKg0KICogQ29weXJpZ2h0IChjKSAyMDA0IEh5YWRl cyBwcm9qZWN0Lg0K
ICogQWxsIHJpZ2h0cyByZXNlcnZlZC4gICBUaGlzIHByb2dyYW0gYW5kIHRo ZSBhY2NvbXBhbnlp
bmcgbWF0ZXJpYWxzDQogKiBhcmUgbWFkZSBhdmFpbGFibGUgdW5kZXIgdGhl IHRlcm1zIG9mIHRo
ZSBDb21tb24gUHVibGljIExpY2Vuc2UgdjEuMA0KICogd2hpY2ggYWNjb21w YW5pZXMgdGhpcyBk
aXN0cmlidXRpb24sIGFuZCBpcyBhdmFpbGFibGUgYXQNCiAqIGh0dHA6Ly93 d3cuZWNsaXBzZS5v
cmcvbGVnYWwvY3BsLXYxMC5odG1sDQogKiANCiAqIENvbnRyaWJ1dG9yczog DQogKiBJQk0gLSBJ
bml0aWFsIEFQSSBhbmQgaW1wbGVtZW50YXRpb24NCiAqKioqKioqKioqKioq KioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq Lw0KDQovKioNCiAq
IFRlc3RwaSB0ZXN0IGNsYXNzIHRvIHZlcmlmeSB0aGUgaGVhZGxlc3MgY2xp ZW50IHN1cHBvcnQg
Zm9yIHRoZSBQcm9maWxpbmcgDQogKiBBZ2VudC4gDQogKiANCiAqIA0KICog QGF1dGhvciBTYW1z
b24gV2FpDQogKiBAYXV0aG9yIFBhdWwgRS4gU2xhdWVud2hpdGUNCiAqIEB2 ZXJzaW9uIEp1bmUg
MjMsIDIwMDUNCiAqIEBzaW5jZSBOb3ZlbWJlciAzLCAyMDAzDQogKi8NCmNs YXNzIFRlc3RwaSB7
DQoNCiAgICBwdWJsaWMgc3RhdGljIHZvaWQgbWFpbihTdHJpbmdbXSBhcmdz KSB7DQoNCiAgICAg
ICAgdHJ5IHsNCg0KICAgICAgICAJUHJvZmlsZXIgcDEgPSBQcm9maWxlci5n ZXRQcm9maWxlcigp
Ow0KICAgICAgICAgICAgaW50IHNlYyA9IDMwMDsNCiAgICAgICAgICAgIA0K ICAgICAgICAgICAg
cDEuc3RhcnRQcm9maWxpbmcodHJ1ZSk7DQoNCiAgICAgICAgICAgIGlmIChh cmdzLmxlbmd0aCA+
IDApew0KICAgICAgICAgICAgICAgIHNlYyA9IEludGVnZXIudmFsdWVPZihh cmdzWzBdKS5pbnRW
YWx1ZSgpOw0KICAgICAgICAgICAgfQ0KDQogICAgICAgICAgICBTeXN0ZW0u b3V0LnByaW50bG4o
IldhaXQgZm9yICIgKyBzZWMgKyAiIHNlY29uZHMiKTsNCiAgICAgICAgICAg IA0KICAgICAgICAg
ICAgcDEuYW5hbHl6ZUhlYXAoIlNlY3Rpb24gMSIpOw0KDQogICAgICAgICAg ICBmb3IgKGludCBp
ID0gMDsgaSA8IHNlYzsgaSsrKSB7DQogICAgICAgICAgICAgICAgZm9vKDEw MDApOyAvLyBzbGVl
cCBmb3IgMSBzZWMNCiAgICAgICAgICAgIH0NCiAgICAgICAgICAgIA0KICAg ICAgICAgICAgcDEu
YW5hbHl6ZUhlYXAoIlNlY3Rpb24gMiIpOw0KICAgICAgICAgICAgDQogICAg ICAgICAgICBwMS5z
dG9wUHJvZmlsaW5nKCk7DQogICAgICAgIH0gDQogICAgICAgIGNhdGNoIChF eGNlcHRpb24gZSkg
ew0KICAgICAgICAgICAgZS5wcmludFN0YWNrVHJhY2UoKTsNCiAgICAgICAg fQ0KICAgIH0NCg0K
ICAgIHByaXZhdGUgc3RhdGljIHZvaWQgZm9vKGludCBtc2VjKSB7DQogICAg ICAgIA0KICAgIAl0
cnkgew0KICAgICAgICAgICAgU3lzdGVtLm91dC5wcmludCgiLiIpOw0KICAg ICAgICAgICAgVGhy
ZWFkLnNsZWVwKG1zZWMpOw0KICAgICAgICB9IA0KICAgIAljYXRjaCAoRXhj ZXB0aW9uIGUpIHsN
CiAgICAgICAgICAgIGUucHJpbnRTdGFja1RyYWNlKCk7DQogICAgICAgIH0N CiAgICB9DQp9
--=_mixed 0000058A85257132_=--
|
|
| |
| Re: Controlling the profiler programmatically [message #58538 is a reply to message #58372] |
Wed, 15 March 2006 16:55 |
| Eclipse User |
|
|
|
Originally posted by: Navid_Mehregani_nmehrega.ca.ibm.com
--=_mixed 005CBCEA85257132_=
Content-Type: multipart/alternative; boundary="=_alternative 005CBCEA85257132_="
--=_alternative 005CBCEA85257132_=
Content-Type: text/plain; charset="US-ASCII"
This is a good question. I always thought that you can specify the
'filters' parameter when you run something in applicationControlled mode,
but I tried this right now and it doesn't seem to be working. Here's how
you specify the filters parm:
-XrunpiAgent:server=applicationControlled,filters=d:\folder\ myfilters.txt
I'm attaching a sample file you would use for your filters. Give this a
try, if it doesn't work for you either, open another defect
[https://bugs.eclipse.org/bugs/enter_bug.cgi?product=TPTP] and set its
severity to normal.
Your only other option would be to specify your filters when importing
your trace file. In the profiling file import wizard, click on the
'filter' tab and specify your filters there. I realize that this doesn't
solve the issue of the profiler taking too long to generate the trace
file. Hopefully we can address this issue soon after you file the defect.
Navid Mehregani
--=_alternative 005CBCEA85257132_=
Content-Type: text/html; charset="US-ASCII"
<br><font size=2 face="sans-serif">This is a good question. I always
thought that you can specify the 'filters' parameter when you run something
in applicationControlled mode, but I tried this right now and it doesn't
seem to be working. Here's how you specify the filters parm:</font>
<br>
<br><font size=2 face="sans-serif"> -XrunpiAgent:server=applicationControlled,filters=d:\folder\ myfilters.txt </font>
<br>
<br><font size=2 face="sans-serif">I'm attaching a sample file you would
use for your filters. Give this a try, if it doesn't work for you
either, open another defect [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=TPTP]
and set its severity to normal. </font>
<br>
<br><font size=2 face="sans-serif">Your only other option would be to specify
your filters when importing your trace file. In the profiling file
import wizard, click on the 'filter' tab and specify your filters there.
I realize that this doesn't solve the issue of the profiler taking
too long to generate the trace file. Hopefully we can address this
issue soon after you file the defect.</font>
<br>
<br><font size=2 face="sans-serif">Navid Mehregani</font>
<br>
<br>
<br>
--=_alternative 005CBCEA85257132_=--
--=_mixed 005CBCEA85257132_=
Content-Type: text/plain; name="filters.txt"
Content-Disposition: attachment; filename="filters.txt"
Content-Transfer-Encoding: quoted-printable
java* * EXCLUDE
sun* * EXCLUDE
com.sun.* * EXCLUDE
com.ibm.* * EXCLUDE
org.eclipse.* * EXCLUDE
org.apache.* * EXCLUDE
org.w3c.* * EXCLUDE
org.xml.* * EXCLUDE
javax.xml.parsers.* * EXCLUDE
--=_mixed 005CBCEA85257132_=--
|
|
|
| Re: Controlling the profiler programmatically [message #58640 is a reply to message #58538] |
Wed, 15 March 2006 21:40 |
Michael Moser
Messages: 914
Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0015_01C64881.698DF590
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Just tried the filters option as described (filtering away all but a =
single class) and again got a HUGE file (670+ MB) although I had =
drastically reduced a couple of loop parameters in my testcase. I =
aborted the import of that file after about 10 mins. (by when it had =
processed about 12%).
So obviously this is indeed not working. I'll file the defect as =
suggested.
Michael
<Navid_Mehregani_nmehrega@ca.ibm.com> wrote in message =
news:dv9gtu$1lc$1@utils.eclipse.org...
This is a good question. I always thought that you can specify the =
'filters' parameter when you run something in applicationControlled =
mode, but I tried this right now and it doesn't seem to be working. =
Here's how you specify the filters parm:=20
-XrunpiAgent:server=3DapplicationControlled,filters=3Dd:\fol der\myfilters=
..txt=20
I'm attaching a sample file you would use for your filters. Give this a =
try, if it doesn't work for you either, open another defect =
[https://bugs.eclipse.org/bugs/enter_bug.cgi?product=3DTPTP] and set its =
severity to normal. =20
Your only other option would be to specify your filters when importing =
your trace file. In the profiling file import wizard, click on the =
'filter' tab and specify your filters there. I realize that this =
doesn't solve the issue of the profiler taking too long to generate the =
trace file. Hopefully we can address this issue soon after you file the =
defect.=20
Navid Mehregani=20
------=_NextPart_000_0015_01C64881.698DF590
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2802" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Just tried the filters option as =
described=20
(filtering away all but a single class) and again got a HUGE file (670+ =
MB)=20
although I had drastically reduced a couple of loop parameters in my =
testcase. I=20
aborted the import of that file after about 10 mins. (by when it had =
processed=20
about 12%).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>So obviously this is indeed =
not working. I'll=20
file the defect as suggested.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Michael</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><<A=20
href=3D"mailto:Navid_Mehregani_nmehrega@ca.ibm.com">Navid_Mehregani_nmehr=
ega@ca.ibm.com</A>>=20
wrote in message <A=20
href=3D"news:dv9gtu$1lc$1@utils.eclipse.org">news:dv9gtu$1lc$1@utils.ecli=
pse.org</A>...</DIV><BR><FONT=20
face=3Dsans-serif size=3D2>This is a good question. I always =
thought that you=20
can specify the 'filters' parameter when you run something in=20
applicationControlled mode, but I tried this right now and it doesn't =
seem to be=20
working. Here's how you specify the filters parm:</FONT> =
<BR><BR><FONT=20
face=3Dsans-serif=20
size=3D2> -XrunpiAgent:server=3DapplicationControlled,filters=3Dd:\fol der\=
myfilters.txt</FONT>=20
<BR><BR><FONT face=3Dsans-serif size=3D2>I'm attaching a sample file you =
would use=20
for your filters. Give this a try, if it doesn't work for you =
either, open=20
another defect =
[https://bugs.eclipse.org/bugs/enter_bug.cgi?product=3DTPTP] and=20
set its severity to normal. </FONT> <BR><BR><FONT =
face=3Dsans-serif=20
size=3D2>Your only other option would be to specify your filters when =
importing=20
your trace file. In the profiling file import wizard, click on the =
'filter' tab and specify your filters there. I realize that this =
doesn't=20
solve the issue of the profiler taking too long to generate the trace =
file.=20
Hopefully we can address this issue soon after you file the =
defect.</FONT>=20
<BR><BR><FONT face=3Dsans-serif size=3D2>Navid Mehregani</FONT>=20
<BR><BR><BR></BODY></HTML>
------=_NextPart_000_0015_01C64881.698DF590--
|
|
|
Goto Forum:
Current Time: Sat Nov 23 10:43:22 GMT 2024
Powered by FUDForum. Page generated in 0.04570 seconds |
] 
Search
Help
Register
Login
Home
