<br clear="all"><br><div class="gmail_quote">On Thu, Oct 21, 2010 at 3:29 AM, Karanbir Singh <span dir="ltr"><<a href="mailto:mail-lists@karan.org">mail-lists@karan.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On 10/21/2010 12:01 AM, Grant McWilliams wrote:<br>
> So what we're on the verge of doing here is creating a test set... I'd<br>
> love to see a shell script that ran a bunch of tests, gathered data<br>
> about the system and then created an archive that would then be uploaded<br>
> to a website which created graphs. Dreaming maybe but it would be<br>
> consistent. So what goes in our testset?<br>
<br>
</div>I am trying to create just that - a kickstart that will build a machine<br>
as a Xen dom0, build 4 domU's, fire up puppet inside the domU's do the<br>
testing and scp results into a central git repo. Then something similar<br>
for KVM.<br>
<br>
will get the basic framework online today.<br>
<div><div></div><div class="h5"><br>
- KB<br>
______</div></div></blockquote><div><br>Do you suppose you could get it to use Phoronix Test Suite so<br>we can start to have measurable stats? We could do the same thing for any VM software - even<br>the ones that don't allow publishing stats in the EULA... <br>
<br>I'm also wondering if we should do the whole test suite or a subset. <br>Here is the list of tests..<br><br>aio-stress<br>apache<br>battery-power-usage<br>blogbench<br>bork<br>build-apache<br>build-imagemagick<br>
build-linux-kernel<br>build-mplayer<br>build-mysql<br>build-php<br>bullet<br>bwfirt<br>byte<br>c-ray<br>cachebench<br>compilebench<br>compliance-acpi<br>compliance-sensors<br>compress-7zip<br>compress-gzip<br>compress-lzma<br>
compress-pbzip2<br>crafty<br>dbench<br>dcraw<br>doom3<br>encode-ape<br>encode-flac<br>encode-mp3<br>encode-ogg<br>encode-wavpack<br>espeak<br>et<br>etqw-demo-iqc<br>etqw-demo<br>etqw<br>ffmpeg<br>fhourstones<br>fio<br>fs-mark<br>
gcrypt<br>geekbench<br>gluxmark<br>gmpbench<br>gnupg<br>graphics-magick<br>gtkperf<br>hdparm-read<br>himeno<br>hmmer<br>idle-power-usage<br>idle<br>iozone<br>j2dbench<br>java-scimark2<br>jgfxbat<br>john-the-ripper<br>juliagpu<br>
jxrendermark<br>lightsmark<br>mafft<br>mandelbulbgpu<br>mandelgpu<br>mencoder<br>minion<br>mrbayes<br>n-queens<br>nero2d<br>network-loopback<br>nexuiz-iqc<br>nexuiz<br>npb<br>openarena<br>openssl<br>opstone-svd<br>opstone-svsp<br>
opstone-vsp<br>padman<br>pgbench<br>phpbench<br>postmark<br>povray<br>prey<br>pybench<br>pyopencl<br>qgears2<br>quake4<br>ramspeed<br>render-bench<br>scimark2<br>smallpt-gpu<br>smallpt<br>smokin-guns<br>specviewperf10<br>
specviewperf9<br>sqlite<br>stream<br>stresscpu2<br>sudokut<br>sunflow<br>supertuxkart<br>systester<br>tachyon<br>tiobench<br>tremulous<br>trislam<br>tscp<br>ttsiod-renderer<br>unigine-heaven<br>unigine-sanctuary<br>unigine-tropics<br>
unpack-linux<br>urbanterror<br>ut2004-demo<br>vdrift-fps-monitor<br>vdrift<br>video-cpu-usage<br>video-extensions<br>warsow<br>wine-cloth<br>wine-domino<br>wine-fire2<br>wine-hdr<br>wine-metaballs<br>wine-vf2<br>wine-water<br>
x11perf<br>x264<br>xplane9-iqc<br>xplane9<br>yafray<br><br><br><br>Grant McWilliams<br><br>.<br><br><br> </div></div><br>