I like the idea of making the test framework a config module and putting the tests themselves in labs. That's cool!
On Sep 6, 2007, at 5:49 AM, Geert Bevin wrote: > Hi, > > I committed new perf tests for Terracotta Cache, based on the > current code-based and the mavenization. The tests are located in > 'perfTests/tests/terracotta-cache'. > > To be able to run them, some config modules should be installed and > the repository location should probably be correctly setup in the > tc-config.xml files (not sure which location to put in there). The > config modules that should be installed are: > > * https://svn.terracotta.org/repo/forge/projects/labs/terracotta- > cache/trunk/ > > - svn co > - mvn install > > * https://svn.terracotta.org/repo/forge/projects/labs/terracotta- > cache/branches/terracotta-autolock/ > > - svn co > - for each dir do "mvn install" > > * http://sourceforge.net/cvs/?group_id=199417 > > - cvs login > - cvs co > - mvn install > > The modules installed by all these should be sufficient to run the > perf tests. > > Another thing to note is that I worked off of Steve's JDistPerfTest > project and enhanced it so that it would work well with the > standard perf test scripts that we have setup. The up-side is that > this should provide a uniform framework and execution scripts for > upcoming perf tests. To create new ones, a new PerformanceAction > simple has to be implemented and the rest of the infrastructure is > setup 'for free'. > > One thing to note is that there are several configuration > parameters that are used by the perf tests (some could be ignore > since they're up to the individual action implementation): > > * clientCount: number of clients that are started > * clientThreadCount: number of threads per client > * testDuration: how long the perf test is ran > * actionClass: which action class will be executed for the test > * onlyRetrieveFromLocalNode (action specific - default false): > forces the 'gets' to only operate on the local node > * disableEvictor (action specific - default false): > disables the evictor > * writePercentage (action specific - default 1): > tunes how often a write occurs wrt. the reads > > Is it possible to run this on the QA servers and see if everything > works as it should? > > Thanks, > > Geert > > > -- > Geert Bevin > Terracotta - http://www.terracotta.org > Uwyn "Use what you need" - http://uwyn.com > RIFE Java application framework - http://rifers.org > Music and words - http://gbevin.com > _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
