[jbosscache-commits] JBoss Cache SVN: r5778 - benchmarks/benchmark-fwk/trunk/conf.
jbosscache-commits at lists.jboss.org
jbosscache-commits at lists.jboss.org
Wed Apr 30 12:42:58 EDT 2008
Author: mircea.markus
Date: 2008-04-30 12:42:58 -0400 (Wed, 30 Apr 2008)
New Revision: 5778
Modified:
benchmarks/benchmark-fwk/trunk/conf/cachebench.xml
Log:
rollback
Modified: benchmarks/benchmark-fwk/trunk/conf/cachebench.xml
===================================================================
--- benchmarks/benchmark-fwk/trunk/conf/cachebench.xml 2008-04-30 16:24:51 UTC (rev 5777)
+++ benchmarks/benchmark-fwk/trunk/conf/cachebench.xml 2008-04-30 16:42:58 UTC (rev 5778)
@@ -8,7 +8,8 @@
emptyCacheBetweenTests - again, use if you're running out of mem.
numThreads - the number of executor threads to use to perform the required number of operations.
-->
-<cachebench sampleSize="10000" gcBetweenTestsEnabled="true" sleepBetweenTests="1000" emptyCacheBetweenTests="true" numThreads="10">
+<cachebench sampleSize="10000" gcBetweenTestsEnabled="true" sleepBetweenTests="1000" emptyCacheBetweenTests="true"
+ numThreads="10">
<!--
@@ -16,19 +17,19 @@
otherwise (part of) cluster operations do not replicate on all instances. We configure here one socket addresses
on each cluster node, so that the framework can communicate with all the nodes and barrier whenever needed.
- for each node instance socket address is specified. You can make sure that addresses are available by using
- checkClusterAddresses ant target
+ checkClusterAddresses ant target
-->
- <cluster bindAddress="127.0.0.1">
- <member host="127.0.0.1" port="7901"/>
- <member host="127.0.0.1" port="7902"/>
- <member host="127.0.0.1" port="7903"/>
- <member host="127.0.0.1" port="7904"/>
- <member host="127.0.0.1" port="7905"/>
- <member host="127.0.0.1" port="7906"/>
- <member host="127.0.0.1" port="7907"/>
- <member host="127.0.0.1" port="7908"/>
- <member host="127.0.0.1" port="7909"/>
- <member host="127.0.0.1" port="7910"/>
+ <cluster>
+ <member host="cluster01" port="17900"/>
+ <member host="cluster02" port="17900"/>
+ <member host="cluster03" port="17900"/>
+ <member host="cluster04" port="17900"/>
+ <member host="cluster05" port="17900"/>
+ <member host="cluster06" port="17900"/>
+ <member host="cluster07" port="17900"/>
+ <member host="cluster08" port="17900"/>
+ <member host="cluster09" port="17900"/>
+ <member host="cluster10" port="17900"/>
</cluster>
<!--
@@ -37,7 +38,7 @@
testcase. By default set to true.
-->
- <testcase name="WebSessionReplicationTest" stopOnFailure="true">
+ <testcase name="WebSessionReplicationTest" stopOnFailure="true">
<!-- org.cachebench.warmup.PutGetCacheWarmup warms up the cache by doing operation on it; simulates a real-world environment.
If no warmup is needed use org.cachebench.warmup.NoCacheWarmup
@@ -50,48 +51,46 @@
validates that replication is enabled and works. If repl does not occur and the stopOnFailure is set to true then exists.
Should be used to make sure that replication is enabled; see javadoc for more details
-->
- <!--
- <test name="replicationOccurrsTest" testClass="org.cachebench.tests.ReplicationOccursTest">
- <param name="partialReplication" value="true"/>
- </test>
+ <test name="replicationOccurrsTest" testClass="org.cachebench.tests.ReplicationOccursTest">
+ <param name="partialReplication" value="true"/>
+ </test>
--->
<!--
* The "name" attrib is just used for display in the reports.
* You can write your own custom testClass.
* weight is currently unused.
-->
- <!--<test name="Strings" testClass="org.cachebench.tests.simpletests.StringTest" weight="2.0" />-->
-
- <test name="SessionSimulator" testClass="org.cachebench.tests.SessionSimulatorTest" weight="2.0" >
- <param name="numberOfRequest" value="100000"/>
- <param name="numberOfAttributes" value="100"/>
- <param name="writePercentage" value="20"/>
- <param name="sizeOfAnAttribute" value="1000"/>
- </test>
+ <!--<test name="Strings" testClass="org.cachebench.tests.simpletests.StringTest" weight="2.0" />-->
- <!--
- <test name="Primitive Wrappers" testClass="org.cachebench.tests.simpletests.PrimitiveTest" weight="1.0" />
- <test name="Custom Class Types" testClass="org.cachebench.tests.simpletests.CustomClassTest" weight="1.0" />
- <test name="Custom Subclasses of Abstracts" testClass="org.cachebench.tests.simpletests.SubclassTest" weight="1.5" />
- <test name="Custom Types With Transients" testClass="org.cachebench.tests.simpletests.TransientTest" weight="1.0" />
- <test name="Custom Types With Statics" testClass="org.cachebench.tests.simpletests.StaticsTest" weight="1.5" />
- <test name="Custom Types With Associations" testClass="org.cachebench.tests.simpletests.AssociationsTest" weight="2.0" />
- -->
+ <test name="SessionSimulator" testClass="org.cachebench.tests.SessionSimulatorTest" weight="2.0">
+ <param name="numberOfRequest" value="100000"/>
+ <param name="numberOfAttributes" value="100"/>
+ <param name="writePercentage" value="20"/>
+ <param name="sizeOfAnAttribute" value="1000"/>
+ </test>
- <!-- WARNING - Configuration file name is now DEPRECATED and will be ignored. Please pass in your cache config
- file name that you wish to use with the -DcacheBenchFwk.cacheConfigFile JVM parameter. The runNode.sh
- and cluster.sh scripts will also do this for you. -->
+ <!--
+ <test name="Primitive Wrappers" testClass="org.cachebench.tests.simpletests.PrimitiveTest" weight="1.0" />
+ <test name="Custom Class Types" testClass="org.cachebench.tests.simpletests.CustomClassTest" weight="1.0" />
+ <test name="Custom Subclasses of Abstracts" testClass="org.cachebench.tests.simpletests.SubclassTest" weight="1.5" />
+ <test name="Custom Types With Transients" testClass="org.cachebench.tests.simpletests.TransientTest" weight="1.0" />
+ <test name="Custom Types With Statics" testClass="org.cachebench.tests.simpletests.StaticsTest" weight="1.5" />
+ <test name="Custom Types With Associations" testClass="org.cachebench.tests.simpletests.AssociationsTest" weight="2.0" />
+ -->
+
+ <!-- WARNING - Configuration file name is now DEPRECATED and will be ignored. Please pass in your cache config
+file name that you wish to use with the -DcacheBenchFwk.cacheConfigFile JVM parameter. The runNode.sh
+and cluster.sh scripts will also do this for you. -->
</testcase>
- <!--
- Available generators are: CSVReportGenerator and ClusterReportGenerator.
- See javadocs for org.cachebench.reportgenerators.ReportGenerator for writing your
- own report generators such as XML generators, graphic generators, etc
+ <!--
+ Available generators are: CSVReportGenerator and ClusterReportGenerator.
+ See javadocs for org.cachebench.reportgenerators.ReportGenerator for writing your
+ own report generators such as XML generators, graphic generators, etc
-->
<!-- The CSV report generated can be plugged in to a spreadsheet to generate graphs. If 'outputFile is set to
- '-generic-' then the name would be generated as follows: 'performance-<nodeIndexInCluster>.csv' -->
+ '-generic-' then the name would be generated as follows: 'data_<cache-product>_<configuration>_<cluster-size>.csv' -->
<report outputFile="-generic-" generator="org.cachebench.reportgenerators.ClusterReportGenerator"/>
</cachebench>
More information about the jbosscache-commits
mailing list