Hi,<br><br>Another thing that might be interested to test is the best eviction algorithm to be used in a certain scenario.<br>Given a context(client), an eviction algorithm is &#39;better&#39; than another one if it manages to return more cached elements, as client ask for them.
<br>(any other definitions of &#39;better&#39; when it comes to eviction policies?) <br>As the benchmark supports multiple configs, it might be useful in helping clients to fine tune their eviction policies. <br><br>Cheers,
<br>Mircea<br><br><div><span class="gmail_quote">On 3/13/07, <b class="gmail_sendername">Manik Surtani</b> &lt;<a href="mailto:manik@jboss.org">manik@jboss.org</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
One of the things I want o do before releasing 2.0.0.BETA2 is to get<br>some idea of performance, with respect to earlier versions of JBoss<br>Cache.&nbsp;&nbsp;As such, I dug up something I started a couple of years ago,<br>the CacheBenchFwk, and tidied a few things up.
<br><br>If you are interested in this, have a look at:<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jboss/CacheBenchFwk/">http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jboss/CacheBenchFwk/</a><br><br>If you have commit rights on JBoss Cache then you&#39;d probably have the
<br>same on this as well.<br><br>In a nutshell, here&#39;s what the framework does:<br><br>* Supports multiple cache products/versions/configs<br>* Allows you to write your own test cases<br>* Comes with some standard test cases
<br>* Produces simple CSV reports which you can import into your<br>favourite spreadsheet software and generate graphs<br><br>Here are some of the things I added today:<br><br>* Basic replicated cache support (see docs/Documentation.txt for
<br>details)<br><br>Some of the things I&#39;d like to add:<br><br>* Automated agent-based testing where each node in the cluster is<br>stressed equally and data is measured on all nodes<br>* Add throughput to the TestResult class
<br>* Automate the process of starting remote instances based on<br>configuration settings<br><br>Have a look, let me know your thoughts.&nbsp;&nbsp;I&#39;m sure there are many<br>areas for improvement, in terms of how the tests are run, reports
<br>generated, etc.&nbsp;&nbsp;As we start testing on bigger and bigger clusters,<br>such frameworks could be very useful.<br><br>Cheers,<br>--<br>Manik Surtani<br><br>Lead, JBoss Cache<br>JBoss, a division of Red Hat<br><br>Email: 
<a href="mailto:manik@jboss.org">manik@jboss.org</a><br>Telephone: +44 7786 702 706<br>MSN: <a href="mailto:manik@surtani.org">manik@surtani.org</a><br>Yahoo/AIM/Skype: maniksurtani<br><br><br>_______________________________________________
<br>jbosscache-dev mailing list<br><a href="mailto:jbosscache-dev@lists.jboss.org">jbosscache-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/jbosscache-dev">https://lists.jboss.org/mailman/listinfo/jbosscache-dev
</a><br></blockquote></div><br>