iirc Andy Fingerhut started benchmarking Clojure programs more than a year before Clojure was even included in the benchmarks game.
https://github.com/jafingerhut/clojure-benchmarks
Here's another thread "Comparing clojure speed to java speed" which has nothing what-so-ever to do with the benchmarks game -
http://groups.google.com/group/clojure/browse_thread/thread/...
(Incidentally, those "hotspot knobs" made the Clojure programs slightly slower but forced collection of the temporary objects that were showing up as much greater memory use than the Java programs.)
I pointed out how comical it is for someone to declare they dislike (who knows why?) the benchmarks game, and then present the benchmarks game to others as a reliable source of information.
(However, although you provided a different URL you did not point out that you thought the parent had linked to the wrong comparison.)
You didn't just "correct" the link to show F# and Clojure.
You changed the link from quad-core to single core and that reduced the difference shown between F# on Mono and Clojure.
Look, the results aren't usefully different: http://shootout.alioth.debian.org/u32q/benchmark.php?test=al...
You do seem to be using the what you dislike and what you are not presenting as reliable to suggest "F# on mono and Clojure (which is slower than plain Java) look pretty similar".
If you really dislike the benchmarks game, don't look at the benchmarks game and don't show it to other people :-)
Most FP communities (incl clojure) have devote non-negligible blocks of time to code review and benchmarking to make sure that at the very least poorly written code isnt' submitted (and the right hotspot knobs are on).
http://groups.google.com/group/clojure/browse_frm/thread/d27...