@tgxworld - Well, its open source so there is no problem about my code not being opened. The thing is that i just have the image of how it shold look like at the end, and also to be able to download and test all versions localy with my suit.
I think best for us is to split the work, as i am focusing on ruby, u made site called (railsbench ) so probably u should focus on benchmarking rails. - also i am trying to make my suit opened to all benchmarks so when u paste some code in benchmark fodler it should test it - not working now, its feature for future. Also I have build an API so everyone can download results and make some stats on his own (each benchmark is running 20-30 times ). I want to try memory benchmarks also
Also as i see the only thing splitting us is that your approach is to make commit based benchmarking while my approach is to make version based benchmarking (as its not possible to download benchmark suit and try to test all commits localy )
So my suggestion is we split the work and make brother sites (railsbench, rubybench) - which will deeply focus on their own benchmarks