[Mono-list] lies and microbenmarks (Was: Mono 0.23 windows installer)

[Brian Deacon]

I ducked my head in fear when I saw this thread start up... but
apparently this is not a verbotten subject.  What is the distinction
between this discussion and the benchmarking that is apparently
forbidden in the license from MS and explicitly discouraged by Miguel on
go-mono?

Brian


> >   - CSC speeds up MS more than Mono (somewhat expected)
> 
> mcs inserts useless additional variables with the pre/post
> increment/decrement operators, and that makes the jit produce somewhat
> worse code, there is already a bug filed for that.
> 
> >   - while many of the mono slowdowns seem related to JIT
> >     optimizations (which the new JIT will change and improve),
> >     the 2x slowdown in index_string_test points to a string,
> >     hashing, memory allocation, or other hashtable inefficiency
> 
> Yes, this issue should be investigated. We already discussed in the past
> about storing the calculated hashvalue for strings: that may help
> somewhat. Serge measured our hashtable implementation using the MS
> runtime and the speed was comparable to their implementation.
> The other issue is memory allocation: in the tests a lot of boxing
> operations take place, I have a simple patch that speeds up both
> index_test and index_string_test by about 10%, though it can be improved.
> 
> lupus