<li>The tree pane displays data collectors at root level and analysis types 

	<li>The tree pane displays data collectors at root level and analysis types 

	as the children of the data collector. Expand the 'Java Profiling' data 

	as the children of the data collector. Expand the 'Java Profiling' data 

	collector and notice the analysis types that fall under it (for example: 

	collector and notice the analysis types that fall under it (for example: 

	Select the analysis types that you are interested in under the 'Java 

	Select the analysis types that you are interested in under the 'Java 

	Profiling' data collector. The features supported for profiling Java 1.5 and 

	Profiling' data collector. The features supported for profiling Java 1.5 and 

	Java 1.4 based java virtual machines are described below.

	Java 1.4 based java virtual machines are described below.

	the JVMPI-based Profiler. Instead of relying on VM-generated events for 

	the JVMPI-based Profiler. Instead of relying on VM-generated events for 

	monitoring application behavior (such as method entry and exit events, 

	monitoring application behavior (such as method entry and exit events, 

	object allocations and so on) it uses Byte Code Instrumentation (BCI) to 

	object allocations and so on) it uses Byte Code Instrumentation (BCI) to 

	technique allows for efficient monitoring of specific parts of the 

	technique allows for efficient monitoring of specific parts of the 

	application, without imposing a noticeable overhead on other parts of the 

	application, without imposing a noticeable overhead on other parts of the 

	and scales well for large applications. </p>

	and scales well for large applications. </p>

	<h3>Execution Profile of an Application</h3>

	<h3>Execution Profile of an Application</h3>

	<p>The Java profiler can be used to profile any Eclipse Plugins, Eclipse RCP 

	<p>The Java profiler can be used to profile any Eclipse Plugins, Eclipse RCP 

	(see <a href="#Profile_Drop_Down_Menu_">Figure</a>). This opens the profile 

	(see <a href="#Profile_Drop_Down_Menu_">Figure</a>). This opens the profile 

	launch configuration window. </p>

	launch configuration window. </p>

	<blockquote>

	<blockquote>

		<p><img src="../images/img_prof_dr_dn.png" border="0"><br>

		<p><img src="../images/img_prof_dr_dn.png" border="0"><br>

	</blockquote>

	</blockquote>

	<p>&nbsp;<br>

	<p>&nbsp;<br>

	Perform the following steps:

	Perform the following steps:

	<ul>

	<ul>

		<li>Create a new launch item of type &quot;Java Application&quot;. 

		<li>Create a new launch item of type &quot;Java Application&quot;. 

		</li>

		</li>

		<a href="#The_Profile_Launch_Configuration_">Figure</a>. <br>

		<a href="#The_Profile_Launch_Configuration_">Figure</a>. <br>

		<br>

		<br>

		<img src="../images/img_prof_launch.png" border="0"><br>

		<img src="../images/img_prof_launch.png" border="0"><br>

		<br>

		<br>

		&nbsp; </li>

		&nbsp; </li>

	</ul>

	</ul>

	<ul>

	<ul>

		</li>

		</li>

		<li>Select &quot;Memory Analysis&quot;(see <a href="#Select_Memory_Analysis">

		<li>Select &quot;Memory Analysis&quot;(see <a href="#Select_Memory_Analysis">

		</li>

		</li>

		<li>If you would like to track the source of your object allocation, 

		<li>If you would like to track the source of your object allocation, 

		box.<br>

		box.<br>

		<br>

		<br>

		&nbsp; </li>

		&nbsp; </li>

	</ul>

	</ul>

	<ul>

	<ul>

		</li>

		</li>

		<br>

		<br>

	</ul>

	</ul>

	<p>&nbsp;</p>

	<p>&nbsp;</p>

	<p>&nbsp;</p>

	<p>&nbsp;</p>

	<p>Java Profiler supports Java 1.4 and lower profiling. The profiler enables 

	<p>Java Profiler supports Java 1.4 and lower profiling. The profiler enables 

	profiling for determining performance bottlenecks and memory analysis of 

	profiling for determining performance bottlenecks and memory analysis of 

	your application.</p>

	your application.</p>

	<p>The Java profiler enables support of multiple analysis types. Depending 

	<p>The Java profiler enables support of multiple analysis types. Depending 

	on the size of the application and the type of analysis required, limit the 

	on the size of the application and the type of analysis required, limit the 

	number of analysis types to be selected for your profiling session. Refer to 

	number of analysis types to be selected for your profiling session. Refer to 

			<td headers="views_avail"><a href="texecstatvw.html">Execution 

			<td headers="views_avail"><a href="texecstatvw.html">Execution 

			Statistics (Package, Class, Method, Instance)</a>,

			Statistics (Package, Class, Method, Instance)</a>,

			<a href="../concepts/cecovsta.htm">Coverage Statistics</a>,

			<a href="../concepts/cecovsta.htm">Coverage Statistics</a>,

			<a href="../ref/reexflwvw.htm">Execution Flow view</a>,

			<a href="../ref/reexflwvw.htm">Execution Flow view</a>,

			<a href="../ref/resqdgvw.htm">UML2 Sequence diagrams views (object,class, 

			<a href="../ref/resqdgvw.htm">UML2 Sequence diagrams views (object,class, 

			thread)</a></td>

			thread)</a></td>

			coverage</a></td>

			coverage</a></td>

		</tr>

		</tr>

	</table>

	</table>

	references by invoking the action <b>Collect Object References</b> to view 

	references by invoking the action <b>Collect Object References</b> to view 

	the profiling data using the Object References view. You can invoke <b>

	the profiling data using the Object References view. You can invoke <b>

	Collect Object References</b> from the toolbar of the Profiling Monitor view 

	Collect Object References</b> from the toolbar of the Profiling Monitor view 

<h2><a name="tefilter_limits">Setting profiling options</a></h2>

<h2><a name="tefilter_limits">Setting profiling options</a></h2>

<p>You can set profiling options for the <b>Java Profiling</b> data collector or 

<p>You can set profiling options for the <b>Java Profiling</b> data collector or 

the selected analysis types, by highlighting the entity and clicking <b>Edit 

the selected analysis types, by highlighting the entity and clicking <b>Edit 

<p>Follow the steps below to set profiling options on the <b>Java Profiling</b> 

<p>Follow the steps below to set profiling options on the <b>Java Profiling</b> 

data collector:</p>

data collector:</p>

<ol>

<ol>

	</li>

	</li>

	</li>

	</li>

	asterisk * can be used as a wildcard in a pattern when specifying package or 

	asterisk * can be used as a wildcard in a pattern when specifying package or 

	method names.<br>

	method names.<br>

	pattern must be specified in one of three ways: 

	pattern must be specified in one of three ways: 

	<ul>

	<ul>

		<li>A pattern with no wildcards, e.g. <tt>org.eclipse.tptp</tt>. 

		<li>A pattern with no wildcards, e.g. <tt>org.eclipse.tptp</tt>. 

		<li>A pattern with a wildcard at the end, e.g. <tt>org.eclipse.*</tt>. 

		<li>A pattern with a wildcard at the end, e.g. <tt>org.eclipse.*</tt>. 

		</li>

		</li>

	</ul>

	</ul>

	regardless of the filter settings. The profiling agent will always collect 

	regardless of the filter settings. The profiling agent will always collect 

	data for objects or classes that are associated with the task being examined 

	data for objects or classes that are associated with the task being examined 

	while collecting data specific to the task. For example, you specify a 

	while collecting data specific to the task. For example, you specify a 

	This behavior applies to threads as well. The <tt>java.lang.Thread</tt> 

	This behavior applies to threads as well. The <tt>java.lang.Thread</tt> 

	class will always show up in the Profiling views because the profiling agent 

	class will always show up in the Profiling views because the profiling agent 

	tracks all running threads, and therefore, collects data for objects or 

	tracks all running threads, and therefore, collects data for objects or 

	on <b>Include</b> under the Rule column for the package, and change it to <b>

	on <b>Include</b> under the Rule column for the package, and change it to <b>

	</li>

	</li>

	</li>

	</li>

	<li>To limit the data collected by method invocations select the <b>Stop 

	<li>To limit the data collected by method invocations select the <b>Stop 

	profiling after specified number of method invocations</b> check box. 

	profiling after specified number of method invocations</b> check box. 

	specified amount of time</b> check box. Specify the amount of time in 

	specified amount of time</b> check box. Specify the amount of time in 

	seconds in the input box provided. 

	seconds in the input box provided. 

	</li>

	</li>

	required to be monitored during the initialization phase (for example 

	required to be monitored during the initialization phase (for example 

	</li>

	</li>

	<li>Click <b>Finish</b> 

	<li>Click <b>Finish</b> 

	</li>

	</li>

	<li>Click <b>Apply</b> to save the changes. </li>

	<li>Click <b>Apply</b> to save the changes. </li>

</ol>

</ol>

<p>Similarly, you can set the options of an analysis type by highlighting it and 

<p>Similarly, you can set the options of an analysis type by highlighting it and 

<h2><a name="tefilter_dest">Configuring the profiling data destination</a></h2>

<h2><a name="tefilter_dest">Configuring the profiling data destination</a></h2>

<p>You can specify the project, and the monitor to use for your profiling 

<p>You can specify the project, and the monitor to use for your profiling 

session. You can also write the profiling data to a file.</p>

session. You can also write the profiling data to a file.</p>

<a href="tecretrc.htm">Profiling an application</a><br>

<a href="tecretrc.htm">Profiling an application</a><br>

<a href="testpref.htm">Setting profiling preferences</a></p>

<a href="testpref.htm">Setting profiling preferences</a></p>

<br>

<br>

Reserved.</p>

Reserved.</p>

<br>

<br>