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

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

Author: whitingjr
Date: 2010-02-22 12:38:47 -0500 (Mon, 22 Feb 2010)
New Revision: 31777

Modified:
   labs/jbosstm/workspace/whitingjr/trunk/performance/README.txt
Log:
Added details of implementation.

Modified: labs/jbosstm/workspace/whitingjr/trunk/performance/README.txt
===================================================================
--- labs/jbosstm/workspace/whitingjr/trunk/performance/README.txt	2010-02-22 17:37:47 UTC (rev 31776)
+++ labs/jbosstm/workspace/whitingjr/trunk/performance/README.txt	2010-02-22 17:38:47 UTC (rev 31777)
@@ -38,13 +38,12 @@
  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.  
+ the 'concat-data' ant task. This cuts out manual cut and paste task.  
  
- 
 Additional information.
 
  The project uses a combination of Ant, JIP and TestNG for executing test cases. To analyse
- the profiling data XSL stylesheets are used for processing XML and generating useful 
+ the profiling data XSL style sheets are used for processing XML and generating useful 
  summary information.
  Some optimisations that change the behaviour of resources participating in transactions are
  supported. Such as the Last Resource Commit Optimisation.
@@ -76,7 +75,9 @@
        and jdbc configuration.
        Added multi threading to test cases.
        Add last resource commit optimisation support.
+       
+0.6    Provide performance capturing using system clock times. Basic timing without
+       incurring overhead.
 
 Known issues:
 
-* Derby database implementation does not support Boolean data type http://issues.apache.org/jira/browse/DERBY-499. The sample data provided using DBUnit import needs Boolean metadata. This makes Derby an unsuitable database to use with this performance framework.