Author: mircea.markus Date: 2008-01-03 02:05:03 -0500 (Thu, 03 Jan 2008) New Revision: 4955 Removed: cache-bench-fwk/trunk/conf/cachebench-coherence.xml cache-bench-fwk/trunk/conf/cachebench-jbc-async.xml cache-bench-fwk/trunk/conf/cachebench-jbc-br-async.xml cache-bench-fwk/trunk/conf/cachebench-jbc-br.xml cache-bench-fwk/trunk/conf/cachebench-jbc-sync.xml Log: removed other onfig files as they are utdated Deleted: cache-bench-fwk/trunk/conf/cachebench-coherence.xml =================================================================== --- cache-bench-fwk/trunk/conf/cachebench-coherence.xml 2008-01-03 06:51:03 UTC (rev 4954) +++ cache-bench-fwk/trunk/conf/cachebench-coherence.xml 2008-01-03 07:05:03 UTC (rev 4955) @@ -1,73 +0,0 @@ -<!-- - Configures and controls the behaviour of the cache benchmarking framework. - - sampleSize - this is the number of putsgets to be performed, an average is used in metrics. - gcBetweenTestsEnabled - if true, the framework pauses between each test and requests System.gc() - use this if you find yourself running out of mem! - sleepBetweenTests - ms to sleep between tests. useful to allow the JVM some time to do a gc - 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="100000" gcBetweenTestsEnabled="true" sleepBetweenTests="1000" emptyCacheBetweenTests="true" numThreads="10"> - - <!-- Each testcase represents either a single configuration or a cacheing product. - - For example, WhirlyCache would be one test case. JBossCache-standalone could be another, JBossCache-replicated could be yet another - - See the javadoc for org.cachebench.CacheWrapper for the cacheWrapper property - --> - - <!-- - Note that if you are using REPLICATED tests, using the "ant runSlave" command, you can only run one test at a time. - Otherwise, if you are using the test in standalone mode (testing a LOCAL cache), you can add multiple "testcase" elements. - --> - - <!-- Make SURE you read the docs - especially when using Terracotta as this involves some additional setup --> - - <!-- Legacy stuff --> - <!--<testcase name="JBossCache140-Pessimistic-REPL_SYNC" cacheWrapper="org.cachebench.cachewrappers.JBossCacheWrapper">--> - <!--<testcase name="EHCache124-replicated" cacheWrapper="org.cachebench.cachewrappers.EHCacheWrapper">--> - <!--<testcase name="Terracotta230" cacheWrapper="org.cachebench.cachewrappers.TerracottaWrapper">--> - - - <!--<testcase name="JBossCache2x-Pessimistic-REPL_SYNC_BR" cacheWrapper="org.cachebench.cachewrappers.JBossCache200Wrapper">--> - <!--<testcase name="JBossCache2x-Pessimistic-REPL_ASYNC" cacheWrapper="org.cachebench.cachewrappers.JBossCache200Wrapper">--> - <testcase name="Coherence-3.x" cacheWrapper="org.cachebench.cachewrappers.CoherenceWrapper"> - - <!-- - * 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.StringTest" weight="2.0" /> - - <!-- - <test name="Primitive Wrappers" testClass="org.cachebench.tests.PrimitiveTest" weight="1.0" /> - <test name="Custom Class Types" testClass="org.cachebench.tests.CustomClassTest" weight="1.0" /> - <test name="Custom Subclasses of Abstracts" testClass="org.cachebench.tests.SubclassTest" weight="1.5" /> - <test name="Custom Types With Transients" testClass="org.cachebench.tests.TransientTest" weight="1.0" /> - <test name="Custom Types With Statics" testClass="org.cachebench.tests.StaticsTest" weight="1.5" /> - <test name="Custom Types With Associations" testClass="org.cachebench.tests.AssociationsTest" weight="2.0" /> - --> - - <!-- arbitrary params may be passed into the cacheWrapper implementation, typically used to pass in config files for the cache product. --> - <!-- JBoss Cache 1.4.x and 2.x --> - <param name="config" value="pess-repl-sync-br.xml" /> - <!--<param name="config" value="pess-repl-async.xml" />--> - - <!-- EHCache --> - <!--<param name="config" value="ehcache-repl-sync.xml" />--> - - <!-- Terracotta --> - <!--<param name="config" value="tc-config-pojo.xml" />--> - </testcase> - - - <!-- Currently we only have a CSVReportGenerator. 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, etc. --> - <report - outputFile="performance.csv" - generator="org.cachebench.reportgenerators.CSVReportGenerator" /> - -</cachebench> Deleted: cache-bench-fwk/trunk/conf/cachebench-jbc-async.xml =================================================================== --- cache-bench-fwk/trunk/conf/cachebench-jbc-async.xml 2008-01-03 06:51:03 UTC (rev 4954) +++ cache-bench-fwk/trunk/conf/cachebench-jbc-async.xml 2008-01-03 07:05:03 UTC (rev 4955) @@ -1,73 +0,0 @@ -<!-- - Configures and controls the behaviour of the cache benchmarking framework. - - sampleSize - this is the number of putsgets to be performed, an average is used in metrics. - gcBetweenTestsEnabled - if true, the framework pauses between each test and requests System.gc() - use this if you find yourself running out of mem! - sleepBetweenTests - ms to sleep between tests. useful to allow the JVM some time to do a gc - 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="100000" gcBetweenTestsEnabled="true" sleepBetweenTests="1000" emptyCacheBetweenTests="true" numThreads="10"> - - <!-- Each testcase represents either a single configuration or a cacheing product. - - For example, WhirlyCache would be one test case. JBossCache-standalone could be another, JBossCache-replicated could be yet another - - See the javadoc for org.cachebench.CacheWrapper for the cacheWrapper property - --> - - <!-- - Note that if you are using REPLICATED tests, using the "ant runSlave" command, you can only run one test at a time. - Otherwise, if you are using the test in standalone mode (testing a LOCAL cache), you can add multiple "testcase" elements. - --> - - <!-- Make SURE you read the docs - especially when using Terracotta as this involves some additional setup --> - - <!-- Legacy stuff --> - <!--<testcase name="JBossCache140-Pessimistic-REPL_SYNC" cacheWrapper="org.cachebench.cachewrappers.JBossCacheWrapper">--> - <!--<testcase name="EHCache124-replicated" cacheWrapper="org.cachebench.cachewrappers.EHCacheWrapper">--> - <!--<testcase name="Terracotta230" cacheWrapper="org.cachebench.cachewrappers.TerracottaWrapper">--> - - - <testcase name="JBossCache2x-Pessimistic-REPL_SYNC_BR" cacheWrapper="org.cachebench.cachewrappers.JBossCache200Wrapper"> - <!--<testcase name="JBossCache2x-Pessimistic-REPL_ASYNC" cacheWrapper="org.cachebench.cachewrappers.JBossCache200Wrapper">--> - <!--<testcase name="Coherence-3.x" cacheWrapper="org.cachebench.cachewrappers.CoherenceWrapper">--> - - <!-- - * 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.StringTest" weight="2.0" /> - - <!-- - <test name="Primitive Wrappers" testClass="org.cachebench.tests.PrimitiveTest" weight="1.0" /> - <test name="Custom Class Types" testClass="org.cachebench.tests.CustomClassTest" weight="1.0" /> - <test name="Custom Subclasses of Abstracts" testClass="org.cachebench.tests.SubclassTest" weight="1.5" /> - <test name="Custom Types With Transients" testClass="org.cachebench.tests.TransientTest" weight="1.0" /> - <test name="Custom Types With Statics" testClass="org.cachebench.tests.StaticsTest" weight="1.5" /> - <test name="Custom Types With Associations" testClass="org.cachebench.tests.AssociationsTest" weight="2.0" /> - --> - - <!-- arbitrary params may be passed into the cacheWrapper implementation, typically used to pass in config files for the cache product. --> - <!-- JBoss Cache 1.4.x and 2.x --> - <!--<param name="config" value="pess-repl-sync-br.xml" /> --> - <param name="config" value="pess-repl-async.xml" /> - - <!-- EHCache --> - <!--<param name="config" value="ehcache-repl-sync.xml" />--> - - <!-- Terracotta --> - <!--<param name="config" value="tc-config-pojo.xml" />--> - </testcase> - - - <!-- Currently we only have a CSVReportGenerator. 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, etc. --> - <report - outputFile="performance.csv" - generator="org.cachebench.reportgenerators.CSVReportGenerator" /> - -</cachebench> Deleted: cache-bench-fwk/trunk/conf/cachebench-jbc-br-async.xml =================================================================== --- cache-bench-fwk/trunk/conf/cachebench-jbc-br-async.xml 2008-01-03 06:51:03 UTC (rev 4954) +++ cache-bench-fwk/trunk/conf/cachebench-jbc-br-async.xml 2008-01-03 07:05:03 UTC (rev 4955) @@ -1,73 +0,0 @@ -<!-- - Configures and controls the behaviour of the cache benchmarking framework. - - sampleSize - this is the number of putsgets to be performed, an average is used in metrics. - gcBetweenTestsEnabled - if true, the framework pauses between each test and requests System.gc() - use this if you find yourself running out of mem! - sleepBetweenTests - ms to sleep between tests. useful to allow the JVM some time to do a gc - 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="100000" gcBetweenTestsEnabled="true" sleepBetweenTests="1000" emptyCacheBetweenTests="true" numThreads="10"> - - <!-- Each testcase represents either a single configuration or a cacheing product. - - For example, WhirlyCache would be one test case. JBossCache-standalone could be another, JBossCache-replicated could be yet another - - See the javadoc for org.cachebench.CacheWrapper for the cacheWrapper property - --> - - <!-- - Note that if you are using REPLICATED tests, using the "ant runSlave" command, you can only run one test at a time. - Otherwise, if you are using the test in standalone mode (testing a LOCAL cache), you can add multiple "testcase" elements. - --> - - <!-- Make SURE you read the docs - especially when using Terracotta as this involves some additional setup --> - - <!-- Legacy stuff --> - <!--<testcase name="JBossCache140-Pessimistic-REPL_SYNC" cacheWrapper="org.cachebench.cachewrappers.JBossCacheWrapper">--> - <!--<testcase name="EHCache124-replicated" cacheWrapper="org.cachebench.cachewrappers.EHCacheWrapper">--> - <!--<testcase name="Terracotta230" cacheWrapper="org.cachebench.cachewrappers.TerracottaWrapper">--> - - - <!--<testcase name="JBossCache2x-Pessimistic-REPL_SYNC_BR" cacheWrapper="org.cachebench.cachewrappers.JBossCache200Wrapper">--> - <testcase name="JBossCache2x-Pessimistic-REPL_ASYNC" cacheWrapper="org.cachebench.cachewrappers.JBossCache200Wrapper"> - <!--<testcase name="Coherence-3.x" cacheWrapper="org.cachebench.cachewrappers.CoherenceWrapper">--> - - <!-- - * 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.StringTest" weight="2.0" /> - - <!-- - <test name="Primitive Wrappers" testClass="org.cachebench.tests.PrimitiveTest" weight="1.0" /> - <test name="Custom Class Types" testClass="org.cachebench.tests.CustomClassTest" weight="1.0" /> - <test name="Custom Subclasses of Abstracts" testClass="org.cachebench.tests.SubclassTest" weight="1.5" /> - <test name="Custom Types With Transients" testClass="org.cachebench.tests.TransientTest" weight="1.0" /> - <test name="Custom Types With Statics" testClass="org.cachebench.tests.StaticsTest" weight="1.5" /> - <test name="Custom Types With Associations" testClass="org.cachebench.tests.AssociationsTest" weight="2.0" /> - --> - - <!-- arbitrary params may be passed into the cacheWrapper implementation, typically used to pass in config files for the cache product. --> - <!-- JBoss Cache 1.4.x and 2.x --> - <!--<param name="config" value="pess-repl-sync-br.xml" /> --> - <param name="config" value="pess-repl-async-br.xml" /> - - <!-- EHCache --> - <!--<param name="config" value="ehcache-repl-sync.xml" />--> - - <!-- Terracotta --> - <!--<param name="config" value="tc-config-pojo.xml" />--> - </testcase> - - - <!-- Currently we only have a CSVReportGenerator. 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, etc. --> - <report - outputFile="performance.csv" - generator="org.cachebench.reportgenerators.CSVReportGenerator" /> - -</cachebench> Deleted: cache-bench-fwk/trunk/conf/cachebench-jbc-br.xml =================================================================== --- cache-bench-fwk/trunk/conf/cachebench-jbc-br.xml 2008-01-03 06:51:03 UTC (rev 4954) +++ cache-bench-fwk/trunk/conf/cachebench-jbc-br.xml 2008-01-03 07:05:03 UTC (rev 4955) @@ -1,73 +0,0 @@ -<!-- - Configures and controls the behaviour of the cache benchmarking framework. - - sampleSize - this is the number of putsgets to be performed, an average is used in metrics. - gcBetweenTestsEnabled - if true, the framework pauses between each test and requests System.gc() - use this if you find yourself running out of mem! - sleepBetweenTests - ms to sleep between tests. useful to allow the JVM some time to do a gc - 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="100000" gcBetweenTestsEnabled="true" sleepBetweenTests="1000" emptyCacheBetweenTests="true" numThreads="10"> - - <!-- Each testcase represents either a single configuration or a cacheing product. - - For example, WhirlyCache would be one test case. JBossCache-standalone could be another, JBossCache-replicated could be yet another - - See the javadoc for org.cachebench.CacheWrapper for the cacheWrapper property - --> - - <!-- - Note that if you are using REPLICATED tests, using the "ant runSlave" command, you can only run one test at a time. - Otherwise, if you are using the test in standalone mode (testing a LOCAL cache), you can add multiple "testcase" elements. - --> - - <!-- Make SURE you read the docs - especially when using Terracotta as this involves some additional setup --> - - <!-- Legacy stuff --> - <!--<testcase name="JBossCache140-Pessimistic-REPL_SYNC" cacheWrapper="org.cachebench.cachewrappers.JBossCacheWrapper">--> - <!--<testcase name="EHCache124-replicated" cacheWrapper="org.cachebench.cachewrappers.EHCacheWrapper">--> - <!--<testcase name="Terracotta230" cacheWrapper="org.cachebench.cachewrappers.TerracottaWrapper">--> - - - <!--<testcase name="JBossCache2x-Pessimistic-REPL_SYNC_BR" cacheWrapper="org.cachebench.cachewrappers.JBossCache200Wrapper">--> - <testcase name="JBossCache2x-Pessimistic-REPL_ASYNC" cacheWrapper="org.cachebench.cachewrappers.JBossCache200Wrapper"> - <!--<testcase name="Coherence-3.x" cacheWrapper="org.cachebench.cachewrappers.CoherenceWrapper">--> - - <!-- - * 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.StringTest" weight="2.0" /> - - <!-- - <test name="Primitive Wrappers" testClass="org.cachebench.tests.PrimitiveTest" weight="1.0" /> - <test name="Custom Class Types" testClass="org.cachebench.tests.CustomClassTest" weight="1.0" /> - <test name="Custom Subclasses of Abstracts" testClass="org.cachebench.tests.SubclassTest" weight="1.5" /> - <test name="Custom Types With Transients" testClass="org.cachebench.tests.TransientTest" weight="1.0" /> - <test name="Custom Types With Statics" testClass="org.cachebench.tests.StaticsTest" weight="1.5" /> - <test name="Custom Types With Associations" testClass="org.cachebench.tests.AssociationsTest" weight="2.0" /> - --> - - <!-- arbitrary params may be passed into the cacheWrapper implementation, typically used to pass in config files for the cache product. --> - <!-- JBoss Cache 1.4.x and 2.x --> - <param name="config" value="pess-repl-sync-br.xml" /> - <!--<param name="config" value="pess-repl-async.xml" />--> - - <!-- EHCache --> - <!--<param name="config" value="ehcache-repl-sync.xml" />--> - - <!-- Terracotta --> - <!--<param name="config" value="tc-config-pojo.xml" />--> - </testcase> - - - <!-- Currently we only have a CSVReportGenerator. 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, etc. --> - <report - outputFile="performance.csv" - generator="org.cachebench.reportgenerators.CSVReportGenerator" /> - -</cachebench> Deleted: cache-bench-fwk/trunk/conf/cachebench-jbc-sync.xml =================================================================== --- cache-bench-fwk/trunk/conf/cachebench-jbc-sync.xml 2008-01-03 06:51:03 UTC (rev 4954) +++ cache-bench-fwk/trunk/conf/cachebench-jbc-sync.xml 2008-01-03 07:05:03 UTC (rev 4955) @@ -1,73 +0,0 @@ -<!-- - Configures and controls the behaviour of the cache benchmarking framework. - - sampleSize - this is the number of putsgets to be performed, an average is used in metrics. - gcBetweenTestsEnabled - if true, the framework pauses between each test and requests System.gc() - use this if you find yourself running out of mem! - sleepBetweenTests - ms to sleep between tests. useful to allow the JVM some time to do a gc - 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="100000" gcBetweenTestsEnabled="true" sleepBetweenTests="1000" emptyCacheBetweenTests="true" numThreads="10"> - - <!-- Each testcase represents either a single configuration or a cacheing product. - - For example, WhirlyCache would be one test case. JBossCache-standalone could be another, JBossCache-replicated could be yet another - - See the javadoc for org.cachebench.CacheWrapper for the cacheWrapper property - --> - - <!-- - Note that if you are using REPLICATED tests, using the "ant runSlave" command, you can only run one test at a time. - Otherwise, if you are using the test in standalone mode (testing a LOCAL cache), you can add multiple "testcase" elements. - --> - - <!-- Make SURE you read the docs - especially when using Terracotta as this involves some additional setup --> - - <!-- Legacy stuff --> - <!--<testcase name="JBossCache140-Pessimistic-REPL_SYNC" cacheWrapper="org.cachebench.cachewrappers.JBossCacheWrapper">--> - <!--<testcase name="EHCache124-replicated" cacheWrapper="org.cachebench.cachewrappers.EHCacheWrapper">--> - <!--<testcase name="Terracotta230" cacheWrapper="org.cachebench.cachewrappers.TerracottaWrapper">--> - - - <testcase name="JBossCache2x-Pessimistic-REPL_SYNC_BR" cacheWrapper="org.cachebench.cachewrappers.JBossCache200Wrapper"> - <!--<testcase name="JBossCache2x-Pessimistic-REPL_ASYNC" cacheWrapper="org.cachebench.cachewrappers.JBossCache200Wrapper">--> - <!--<testcase name="Coherence-3.x" cacheWrapper="org.cachebench.cachewrappers.CoherenceWrapper">--> - - <!-- - * 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.StringTest" weight="2.0" /> - - <!-- - <test name="Primitive Wrappers" testClass="org.cachebench.tests.PrimitiveTest" weight="1.0" /> - <test name="Custom Class Types" testClass="org.cachebench.tests.CustomClassTest" weight="1.0" /> - <test name="Custom Subclasses of Abstracts" testClass="org.cachebench.tests.SubclassTest" weight="1.5" /> - <test name="Custom Types With Transients" testClass="org.cachebench.tests.TransientTest" weight="1.0" /> - <test name="Custom Types With Statics" testClass="org.cachebench.tests.StaticsTest" weight="1.5" /> - <test name="Custom Types With Associations" testClass="org.cachebench.tests.AssociationsTest" weight="2.0" /> - --> - - <!-- arbitrary params may be passed into the cacheWrapper implementation, typically used to pass in config files for the cache product. --> - <!-- JBoss Cache 1.4.x and 2.x --> - <param name="config" value="pess-repl-sync.xml" /> - <!--<param name="config" value="pess-repl-async.xml" />--> - - <!-- EHCache --> - <!--<param name="config" value="ehcache-repl-sync.xml" />--> - - <!-- Terracotta --> - <!--<param name="config" value="tc-config-pojo.xml" />--> - </testcase> - - - <!-- Currently we only have a CSVReportGenerator. 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, etc. --> - <report - outputFile="performance.csv" - generator="org.cachebench.reportgenerators.CSVReportGenerator" /> - -</cachebench>