Attachment 65225 Details for Bug 166578 – Patch with latest fixes

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

[patch] Patch with latest fixes

objref_patch2 (text/plain), 14.69 KB, created by jkubasta

on 2007-04-27 12:19:18 EDT

(hide)

Description:

Filename:

MIME Type:

Creator: jkubasta

Created: 2007-04-27 12:19:18 EDT

Size: 14.69 KB

patch

obsolete

>### Eclipse Workspace Patch 1.0
>#P platform
>Index: org.eclipse.tptp.platform.doc.user/tasks/tefilter.htm
>===================================================================
>RCS file: /cvsroot/tptp/platform/org.eclipse.tptp.platform.doc.user/tasks/tefilter.htm,v
>retrieving revision 1.28
>diff -u -r1.28 tefilter.htm
>--- org.eclipse.tptp.platform.doc.user/tasks/tefilter.htm	25 Apr 2007 03:44:00 -0000	1.28
>+++ org.eclipse.tptp.platform.doc.user/tasks/tefilter.htm	27 Apr 2007 16:16:46 -0000
>@@ -57,7 +57,7 @@
> 	<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 
> 	collector and notice the analysis types that fall under it (for example: 
>-	'Basic Memory Analysis', 'Execution Time Analysis', and so on...). 
>+	'Execution Time Analysis', 'Probe Insertion', and so on...). 
> 	Select the analysis types that you are interested in under the 'Java 
> 	Profiling' data collector. The features supported for profiling Java 1.5 and 
> 	Java 1.4 based java virtual machines are described below.
>@@ -82,10 +82,10 @@
> 	the JVMPI-based Profiler. Instead of relying on VM-generated events for 
> 	monitoring application behavior (such as method entry and exit events, 
> 	object allocations and so on) it uses Byte Code Instrumentation (BCI) to 
>-	inject small pieces of code which tracks the application execution. This 
>+	inject small pieces of code which track the application execution. This 
> 	technique allows for efficient monitoring of specific parts of the 
> 	application, without imposing a noticeable overhead on other parts of the 
>-	application that are not being monitored. This approach is easy to use and 
>+	application that are not being monitored. This approach is easy to use 
> 	and scales well for large applications. 
> 	<h3>Execution Profile of an Application</h3>
> 	The Java profiler can be used to profile any Eclipse Plugins, Eclipse RCP 
>@@ -94,62 +94,80 @@
> 	(see <a href="#Profile_Drop_Down_Menu_">Figure</a>). This opens the profile 
> 	launch configuration window. 
> 	<blockquote>
>+		<a name="Profile_Drop_Down_Menu_">Profile Drop Down Menu</a> 
> 		<img src="../images/img_prof_dr_dn.png" border="0"> 
>-		 
>-		<a name="Profile_Drop_Down_Menu_">Profile Drop Down Menu</a>
>+		
> 	</blockquote>
> 	&nbsp; 
> 	Perform the following steps:
> 	<ul>
> 		<li>Create a new launch item of type &quot;Java Application&quot;. 
> 		</li>
>-		<li>Select the &quot;Monitor&quot; tab as shown in
>+		<li>Select the &quot;Monitor&quot; tab from the profile launch configuration.
>+		<li>Select &quot;Execution Time Analysis&quot;, as shown in
> 		<a href="#The_Profile_Launch_Configuration_">Figure</a>. 
> 		 
>+		<a name="The_Profile_Launch_Configuration_">The Profile Launch 
>+		Configuration</a> 
> 		<img src="../images/img_prof_launch.png" border="0"> 
> 		 
>-		<a name="The_Profile_Launch_Configuration_">The Profile Launch 
>-		Configuration</a> 
>+		
> 		&nbsp; </li>
>+		<li>Click on Edit Options to set any desired filter. 
>+		</li>
> 	</ul>
>-	<h3>Object allocation analysis</h3>
>-	To perform a Object Allocation analysis or Memory analysis (Heap) profile 
>-	your application, select &quot;Profile&quot; from the Profile drop down menu (see
>-	<a href="#img_prof_launch">Figure</a>). 
>-	&nbsp; 
>-	Perform the following steps:
>+	<h3>Memory (Object allocation) analysis</h3>
>+	To perform an Object Allocation analysis or Memory analysis (Heap), perform the following steps:
> 	<ul>
>-		<li>Select the &quot;Monitor&quot; tab as shown in
>-		<a href="#Profile_Drop_Down_Menu_">Figure</a>. 
>-		</li>
>-		<li>Click on Edit options to set any desired filter. 
>+		<li>Profile your application by selecting &quot;Profile&quot; from the Profile drop down menu (see
>+	<a href="#Profile_Drop_Down_Menu_">Figure</a>). </li>
>+		<li>Select the &quot;Monitor&quot; tab from the profile launch configuration.</a>. 
> 		</li>
> 		<li>Select &quot;Memory Analysis&quot;(see <a href="#Select_Memory_Analysis">
>-		Figure</a>). 
>+		Figure</a>).
>+		 
>+		 <a name="Select_Memory_Analysis">Select Memory Analysis</a> 
>+		<img src="../images/img_mem_prof.png" border="0"> 
>+		 
>+		
>+		&nbsp; </li> 
>+		<li>Click on Edit Options to set any desired filter. 
> 		</li>
> 		<li>If you would like to track the source of your object allocation, 
>-		click on Edit options and check the object allocation tracking check 
>+		click on Edit Options and check the Track object allocation sites check 
> 		box. 
>+		</li>
>+	</ul>
>+	
>+	<h3>Thread Profile of an Eclipse Application</h3>
>+	To perform a thread profile of your application, perform the following steps:
>+	<ul>
>+		<li>Select &quot;Profile&quot; from the Profile drop down menu (see <a href="#Profile_Drop_Down_Menu_">Figure</a>).
>+		</li>
>+		<li>Select the &quot;Monitor&quot; tab from the profile launch configuration. 
>+		</li>
>+		<li>Select &quot;Thread Analysis&quot; (see <a href="#Select_Thread_Analysis">
>+		Figure</a>).
>+		 <a name="Select_Thread_Analysis">Select Thread Analysis</a> 
>+		<img src="../images/img_thrd_prof.png" border="0"> 
> 		 
>-		<img src="../images/img_mem_prof.png" border="0"> 
>+		
> 		&nbsp; </li>
> 	</ul>
>-	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a name="Select_Memory_Analysis">Select Memory 
>-	Analysis</a> 
>-	&nbsp; 
>-	<h3>Thread Profile of an Eclipse Application</h3>
>-	To perform a thread profile of your application, select &quot;Profile&quot; from 
>-	the Profile drop down menu (see <a href="#Profile_Drop_Down_Menu_">Figure</a>).
>-	
>-	Perform the following steps:
>+	<h3>Probe Insertion</h3>
>+	To perform analysis using probe insertion, perform the following steps:
> 	<ul>
>-		<li>Select the &quot;Monitor&quot; tab as shown in
>-		<a href="#Profile_Drop_Down_Menu_">Figure</a>. 
>+		<li>Select &quot;Profile&quot; from the Profile drop down menu (see <a href="#Profile_Drop_Down_Menu_">Figure</a>).
> 		</li>
>-		<li>Select &quot;Thread Analysis&quot; (see <a href="#Select_Thread_Analysis_">
>-		Figure</a>). 
>+		<li>Select the &quot;Monitor&quot; tab from the profile launch configuration. 
>+		</li>
>+		<li>Select &quot;Probe Insertion&quot; (see <a href="#Probe_Insertion">
>+		Figure</a>).
>+		 <a name="Probe_Insertion">Select Probe Insertion</a> 
>+		<img src="../images/img_thrd_prof.png" border="0"> 
> 		 
>-		<img src="../images/img_thrd_prof.png" border="0"> </li>
>+		
>+		&nbsp; </li>
> 	</ul>
> 	&nbsp;
> 	&nbsp;
>@@ -159,6 +177,7 @@
> 	Java Profiler supports Java 1.4 and lower profiling. The profiler enables 
> 	profiling for determining performance bottlenecks and memory analysis of 
> 	your application.
>+	 
> 	The Java profiler enables support of multiple analysis types. Depending 
> 	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 
>@@ -233,7 +252,7 @@
> 			<td headers="views_avail"><a href="texecstatvw.html">Execution 
> 			Statistics (Package, Class, Method, Instance)</a>,
> 			<a href="../concepts/cecovsta.htm">Coverage Statistics</a>,
>-			<a href="../ref/reorpane.htm">Object References view*</a>,
>+			<a href="../ref/reorpane.htm">Object References view**</a>,
> 			<a href="../ref/reexflwvw.htm">Execution Flow view</a>,
> 			<a href="../ref/resqdgvw.htm">UML2 Sequence diagrams views (object,class, 
> 			thread)</a></td>
>@@ -250,38 +269,38 @@
> 			coverage</a></td>
> 		</tr>
> 	</table>
>-	* Note: For the Object References view, you will need to collect object 
>+	<h4>Notes:</h4>
>+	* For the Object References view, you will need to collect object 
> 	references by invoking the action Collect Object References to view 
> 	the profiling data using the Object References view. You can invoke 
> 	Collect Object References from the toolbar of the Profiling Monitor view 
>-	or by right clicking on the agent in the Profiling Monitor view.</li>
>-</ol>
>+	or by right clicking on the agent in the Profiling Monitor view.
>+ ** For the Object References view, you will need to collect object 
>+	references by invoking the action Collect Object References to view 
>+	the profiling data using the Object References view. You can invoke 
>+	Collect Object References from the toolbar.
>+
>+
> <h2><a name="tefilter_limits">Setting profiling options</a></h2>
> You can set profiling options for the Java Profiling data collector or 
> the selected analysis types, by highlighting the entity and clicking Edit 
>-Option.
>+Options.
> Follow the steps below to set profiling options on the Java Profiling 
> data collector:
> <ol>
>-	<li>Highlight Java Profiling and click on Edit Option 
>+	<li>Highlight Java Profiling and click on Edit Options 
> 	</li>
>-	<li>On the Filter Set page you can specify the filter set to be applied to 
>-	your profiling session. By default Automatically determine filtering 
>-	criteria check box is selected and the scope of classes for which the 
>-	profiling data is collected is determined automatically by taking in account 
>-	launch configuration type, your project and its' dependencies content and 
>-	active working sets. 
>-	</li>
>-	<li>You can specify the filtering criteria manually by unchecking the 
>-	Automatically determine filtering criteria check box and selecting a 
>-	filter set from the Select a filter set list. For example, you can 
>-	use the Default set. 
>+	<li>By default, all classes are profiled. You can change this on the Filter Set page by specifying
>+	the filter set to be applied to your profiling session. Under the Select a filter set list, click 
>+	Add to add the desired filter set. 
> 	</li>
>-	<li>Under Contents of selected filter set, click Add to add 
>-	packages that you want to collect data for. The Add Filter dialog opens. An 
>+	<li>You can also specify the filtering criteria manually. Under Contents of selected filter set, 
>+	click Add to add packages for which you want to collect data. The Add Filter dialog opens. An 
> 	asterisk * can be used as a wildcard in a pattern when specifying package or 
> 	method names. 
>-	Note 1. When entering a pattern for the package or method name, the 
>+	Notes: 
>+	<ol>
>+	<li>When entering a pattern for the package or method name, the 
> 	pattern must be specified in one of three ways: 
> 	<ul>
> 		<li>A pattern with no wildcards, e.g. <tt>org.eclipse.tptp</tt>. 
>@@ -291,8 +310,8 @@
> 		<li>A pattern with a wildcard at the end, e.g. <tt>org.eclipse.*</tt>. 
> 		</li>
> 	</ul>
>-	 
>-	Note 2. Certain classes will always be visible in the profiling views 
>+	</li>
>+	<li>Certain classes will always be visible in the profiling views 
> 	regardless of the filter settings. The profiling agent will always collect 
> 	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 
>@@ -306,19 +325,17 @@
> 	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 
> 	tracks all running threads, and therefore, collects data for objects or 
>-	classes associated with those threads. 
>-	 
>-&nbsp;</li>
>-	<li>Specify the Package or Class, Method Name and select 
>-	Include from the Rule drop-down list. 
>-&nbsp;</li>
>-	<li>Click OK. The filter criterion is added to the contents list. 
>-	</li>
>-	<li>To exclude other existing packages from the filter contents list, click 
>+	classes associated with those threads.</li>
>+	</ol>
>+	<li>Specify the Package or Class, Method Name that you wish to filter. If you want see the 
>+	profiling data for these packages, classes, methods, select Include from the Rule drop-down list. If 
>+	you want to exclude these packages, classes, methods, from the profiling data click 
> 	on Include under the Rule column for the package, and change it to 
>-	Exclude. 
>+	Exclude.</li> 
>+	<li>Click OK. The filter criterion is added to the contents list. 
> 	</li>
>-	<li>Click Next 
>+	<li>On Java 1.5 and higher, click Finish and proceed to step 11 below. On Java 1.4 and lower, click 
>+	Next and proceed to the next step. 
> 	</li>
> 	<li>To limit the data collected by method invocations select the Stop 
> 	profiling after specified number of method invocations check box. 
>@@ -328,19 +345,21 @@
> 	specified amount of time check box. Specify the amount of time in 
> 	seconds in the input box provided. 
> 	</li>
>-	<li>To start the profiling agent in pause mode so that data is not collected 
>-	during the initialization stage of the application, clear the 
>-	Automatically start monitoring when application is launched check box. 
>-	This option is strongly recommended for large applications that are not 
>+	<li>To start the profiling agent automatically when the application is launched, check the 
>+	Automatically start monitoring when application is launched check box. Note: It is 
>+	strongly recommended for large applications that are not 
> 	required to be monitored during the initialization phase (for example 
>-	launching an instance of the workbench). 
>+	launching an instance of the workbench), that you accept the deafult and leave the deselection of the 
>+	Automatically start monitoring when application is launched check box. This will result in the
>+	profiling agent being started in pause mode so that data is not collected 
>+	during the initialization stage of the application. 
> 	</li>
> 	<li>Click Finish 
> 	</li>
> 	<li>Click Apply to save the changes. </li>
> </ol>
> Similarly, you can set the options of an analysis type by highlighting it and 
>-selecting Edit Option. 
>+selecting Edit Options. 
> <h2><a name="tefilter_dest">Configuring the profiling data destination</a></h2>
> You can specify the project, and the monitor to use for your profiling 
> session. You can also write the profiling data to a file.
>@@ -371,7 +390,7 @@
> <a href="tecretrc.htm">Profiling an application</a> 
> <a href="testpref.htm">Setting profiling preferences</a>
> 
>-&nbsp;(C) Copyright IBM Corporation 2000, 2006. All Rights 
>+&nbsp;(C) Copyright IBM Corporation 2000, 2007. All Rights 
> Reserved.
> 
> &nbsp;

Actions: View | Diff

Attachments on bug 166578: 65139 | 65225 | 65293 | 65294 | 65295 | 65296 | 65299