Author: mircea.markus Date: 2008-10-23 10:59:44 -0400 (Thu, 23 Oct 2008) New Revision: 7007 Modified: benchmarks/benchmark-fwk/trunk/cache-products/terracotta-2.5.0/Readme.txt Log: updated Modified: benchmarks/benchmark-fwk/trunk/cache-products/terracotta-2.5.0/Readme.txt =================================================================== --- benchmarks/benchmark-fwk/trunk/cache-products/terracotta-2.5.0/Readme.txt 2008-10-23 14:33:36 UTC (rev 7006) +++ benchmarks/benchmark-fwk/trunk/cache-products/terracotta-2.5.0/Readme.txt 2008-10-23 14:59:44 UTC (rev 7007) @@ -10,7 +10,10 @@ b) make sure that the jar file generated at 2) is in the class path Note: each line that needs to be changed is prefixed by a comment: "#next line should be modified based on the environment" 4) Before running the tests, make sure you start the TC server first. A server with default configuration can be started using the script: TC_ROOT/samples/start-demo-server.sh -5) Run the tests by by using allJBossCacheTests.sh or runNode.sh +5) Run the tests by by using allJBossCacheTests.sh or runNode.sh. The third parameter of runNode.sh the test config file name, which is missing in the case of Terracotta. + Make sure you supply a meaningful placeholder for this (e.g. 'teracotta-250'), as the BenchmarkFwk relies on this name for prefixing the report file. -Note: steps 1-3 should only be performed once +Notes: + - steps 1-3 should only be performed once + - if you would like to use another Terracotta client config file, update the "-Dtc.config=$THIS_DIR/tc-client-config.xml" part in ./config.sh