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

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

Author: whitingjr
Date: 2009-12-16 11:47:18 -0500 (Wed, 16 Dec 2009)
New Revision: 30717

Modified:
   labs/jbosstm/workspace/whitingjr/trunk/performance/CONFIGURATION.txt
   labs/jbosstm/workspace/whitingjr/trunk/performance/INSTALL.txt
   labs/jbosstm/workspace/whitingjr/trunk/performance/README.txt
Log:
Updated instructions following changes to configure each resource.

Modified: labs/jbosstm/workspace/whitingjr/trunk/performance/CONFIGURATION.txt
===================================================================
--- labs/jbosstm/workspace/whitingjr/trunk/performance/CONFIGURATION.txt	2009-12-16 15:34:18 UTC (rev 30716)
+++ labs/jbosstm/workspace/whitingjr/trunk/performance/CONFIGURATION.txt	2009-12-16 16:47:18 UTC (rev 30717)
@@ -4,7 +4,7 @@
 I want to configure......
 
 * Connection pool size
-src/main/resources/properties/database/shared-database.properties - db-pool-max.size, db-pool-min.size
+src/main/resources/properties/database/<resource.X.db-vendor>/db-profile.properties - db-pool-max.size, db-pool-min.size
 
 * Number of times tests are repeated
 src/test/resources/testsuite-integration-ejb3.xml - test_count 
@@ -13,7 +13,7 @@
 src/test/resources/testsuite-integration-ejb3.xml - warmup_count
 
 * Set the database connection user name and password
-src/main/resources/properties/database/<db-vendor>/database-locations/<db-installation>/db-installation.properties - db-vendor-jdbc-userName, db-vendor-jdbc-password
+src/main/resources/properties/database/<resource.X.db-vendor>/database-locations/<resource.X.db-installation>/db-installation.properties - db-vendor-jdbc-userName, db-vendor-jdbc-password
 
 * Suspend the profiler before starting test, to attatch a debugger.
 build.properties - suspend
@@ -22,8 +22,11 @@
 src/test/resources/testsuite-integration-ejb3.xml - invoke_optional_write
 
 * Select an interesting method for analysis.
-src/main/resources/properties/database/<db-vendor>/db-profile.properties - <db-vendor>.db-vendor.method.xpaths
+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/<db-vendor>/database-locations/<db-installation>/resourceA/resource.properties - db-statement.caching.enabled.X
\ No newline at end of file
+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
+
+* Adjust the number of cached statements
+src/main/resources/properties/database/<resource.X.db-vendor>/db-profile.properties - <resource.X.db-vendor>.db-connection-prepared.statement.cache.size

Modified: labs/jbosstm/workspace/whitingjr/trunk/performance/INSTALL.txt
===================================================================
--- labs/jbosstm/workspace/whitingjr/trunk/performance/INSTALL.txt	2009-12-16 15:34:18 UTC (rev 30716)
+++ labs/jbosstm/workspace/whitingjr/trunk/performance/INSTALL.txt	2009-12-16 16:47:18 UTC (rev 30717)
@@ -15,27 +15,28 @@
    Create a directory (without spaces) for the database vendor if it does not already
    exist.
    ./libs/dbdrivers/<dbvendor>/
-   Place the driver jar file in the. directory.
+   Place the driver jar file in the. directory. This will need repeating if you will
+   be configuring multiple vendors.
    
-   The <dbvendor> directory name is used later in these configuration instructions 
+   The <resource.X.dbvendor> directory name is used later in these configuration instructions 
    and executing the profiling.
    
    Now configure the database connection details for the installation type. Each installation
    supports two resources. The second resource is used for distributed transaction 
    profiling. To select a vendor for each resource use the command line flags:
-   db.vendor=<dbvendor>
-   second.resource.db.vendor=<dbvendor>
+   resource.A.db.vendor=<dbvendor>
+   resource.B.db.vendor=<dbvendor>
    
    For each database vendor three (physical) types of installation are supported. Embedded,
    co-located and remote. The configuration details are repeated for each resource. 
    This allows profiling databases by different vendors to be run concurrently. There is a  
    common vendor properties file per vendor. The resource specific version uses the vendor
    version.
-   ./src/main/resources/properties/database/<dbvendor>/db-profile.properties
+   ./src/main/resources/properties/database/<resource.X.db.vendor>/db-profile.properties
    For each reasource are two configuration files. The first for connection details and
    the second for the resource.
-   ./src/main/resources/properties/database/<dbvendor>/database-locations/<installation>/resource<A|B>/connection.properties
-   ./src/main/resources/properties/database/<dbvendor>/database-locations/<installation>/resource<A|B>/resource.properties
+   ./src/main/resources/properties/database/<resource.X.db.vendor>/database-locations/<installation>/resource<A|B>/connection.properties
+   ./src/main/resources/properties/database/<resource.X.db.vendor>/database-locations/<installation>/resource<A|B>/resource.properties
    
    Configuring the JIP profiler to recognise classes for each vendor requires identifying 
    the package name of the driver library. It is recommended you use a generic name to

Modified: labs/jbosstm/workspace/whitingjr/trunk/performance/README.txt
===================================================================
--- labs/jbosstm/workspace/whitingjr/trunk/performance/README.txt	2009-12-16 15:34:18 UTC (rev 30716)
+++ labs/jbosstm/workspace/whitingjr/trunk/performance/README.txt	2009-12-16 16:47:18 UTC (rev 30717)
@@ -42,6 +42,7 @@
 
 0.5    Supports filtering and merging of results into categories.
        Added support for using different profilers.
+       Added complete control for each resource. Can mix and match vendor, installation type and jdbc configuration.
 
 Known issues: