[jboss-svn-commits] JBL Code SVN: r31517 - labs/jbosstm/workspace/whitingjr/trunk/performance.

[jboss-svn-commits at lists.jboss.org]

Author: whitingjr
Date: 2010-02-09 12:42:11 -0500 (Tue, 09 Feb 2010)
New Revision: 31517

Modified:
   labs/jbosstm/workspace/whitingjr/trunk/performance/CONFIGURATION.txt
   labs/jbosstm/workspace/whitingjr/trunk/performance/README.txt
Log:
Added instructions and details of project.


Modified: labs/jbosstm/workspace/whitingjr/trunk/performance/CONFIGURATION.txt
===================================================================
--- labs/jbosstm/workspace/whitingjr/trunk/performance/CONFIGURATION.txt	2010-02-09 17:30:21 UTC (rev 31516)
+++ labs/jbosstm/workspace/whitingjr/trunk/performance/CONFIGURATION.txt	2010-02-09 17:42:11 UTC (rev 31517)
@@ -21,10 +21,6 @@
 * Enable Read Only optimization in first resource for multiple resource tests.
 src/test/resources/testsuite-integration-ejb3.xml - invoke_optional_write
 
-* Select an interesting method for analysis.
-src/main/resources/properties/database/<resource.X.db-vendor>/db-profile.properties - <resource.X.db-vendor>.db-vendor.method.xpaths
-build.properties - testcase.xpaths
- 
 * Enable/Disable statement caching
 src/main/resources/properties/database/<resource.X.db-vendor>/database-locations/<resource.X.db-installation>/resourceA/resource.properties - <resource.X.db-installation>.db-connection-share.prepared.statements
 
@@ -36,3 +32,4 @@
 
 * Configuring the Last Resource Gambit/Last Resource Commit Optimisation
 src/test/resources/testsuite-integration-ejb3.xml - use_lrco
+

Modified: labs/jbosstm/workspace/whitingjr/trunk/performance/README.txt
===================================================================
--- labs/jbosstm/workspace/whitingjr/trunk/performance/README.txt	2010-02-09 17:30:21 UTC (rev 31516)
+++ labs/jbosstm/workspace/whitingjr/trunk/performance/README.txt	2010-02-09 17:42:11 UTC (rev 31517)
@@ -23,8 +23,24 @@
  categories. Categories can be made up of particular methods. The main categories for this project
  are category-0 which is the whole test method, category-B which is the read and write with 
  resource A, category-C is the read and write for resource B, category-D is the commit and category-A
- is 0-(B+C+D) and is called 'other'.
+ is 0-(B+C+D) which is called 'other'.
+ 
+ The configuration of each category depends on the test case implementation. The recommended technique for
+ creating a test case which can be easily profiled is as follows. The activity in the test
+ case with a resource needs wrapping in separate methods. This allows easy separation of timing
+ for the post-profiling analysis phase. Don't rely on profiling SessionImpl.flush for example 
+ because classes such as these have large numbers of methods. Which as a by product creates 
+ huge amounts of profiling data (and overhead) for capturing only one method which is of
+ interest. Instead profile just the test case and create a separete method.
 
+ The output from the profiling system is a comma separated file. This file is formatted with 
+ the first line as the header. This format is easy to paste into a spreadsheet and manipulate
+ into graphs. There is a template spreadsheet which is created to show the time taken and
+ comparrison of xa and local-tx profiling. The tab page for each jdbc resource type is 
+ an concatination of each csv file in the profiling run. To concatenate the csv file use
+ the 'concat-data' ant task. This cuts out the laborious manual cut and paste task.  
+ 
+ 
 Additional information.
 
  The project uses a combination of Ant, JIP and TestNG for executing test cases. To analyse