|
Hi Daniel,
The stats are embedded in the test itself--this test works by writing something and then looking over at the slave to ensure it made it over. This means that the transaction cost is actually time to write + time to see that it got to the slave.
I wrote that scenario a while ago. Recently I added a new feature to Benchmark that is very handy for master/slave testing and that we use ourselves to benchmark Tungsten performance. There is now an optional add-on called a Monitor that runs along-side the scenario threads and measures slave latency while the test is running. Moreover, the monitor continues to run after the scenario threads terminate, stopping only when the slave is fully caught up.
This new feature is in the current code in SVN. If you are able to use Java, you can just download and build yourself. I'll provide a new build if there is interest.
Cheers, Robert
|