One of the possible exceptions is number crunching. .NET has no equivalent to Mono.SIMD, so for numerical tasks it's conceivable that code written for Mono could end up being far faster.
Depending on what you're doing, the performance difference might not matter in practice. Mono's (historically, at least) done worse with super OO-y code because of its poorer GC performance, but oftentimes that kind of code also ends up appearing in applications where overall performance is dominated by I/O and CPU efficiency ends up being negligible.
Comments
One of the possible exceptions is number crunching. .NET has no equivalent to Mono.SIMD, so for numerical tasks it's conceivable that code written for Mono could end up being far faster.
Depending on what you're doing, the performance difference might not matter in practice. Mono's (historically, at least) done worse with super OO-y code because of its poorer GC performance, but oftentimes that kind of code also ends up appearing in applications where overall performance is dominated by I/O and CPU efficiency ends up being negligible.