[Mono-dev] Fundamental performance problems with Mono

Robert Jordan robertj at gmx.net
Fri Jan 8 08:00:01 EST 2010

On 08.01.2010 13:14, Stifu wrote:
> Hi,
> You may already know, but Mono 2.8 will have a brand new GC... This may
> improve your app performances.

The new GC won't help in this special case.

>> Therefore, I do blame Mono for the poor performance. If the epoll+I/O
>> Thread pool model is implemented correctly and if the managed async socket
>> API is implemented properly (and there is a lot to benefit from the
>> XXXAsync methods) then there is no reason why a Mono server should not be
>> equal in performance to a .NET on Windows server. And again, this is good
>> enough performance for me.

The current async socket implementation is a solely managed one, merely
a wrapper around the 1.1 APIs. There is no runtime support for the new
async socket APIs introduced with .NET 2.0.

So you're actually blaming a wrapper whose solely intention was
to gain .NET 2.0 compatibility.

Patches welcome :)


More information about the Mono-devel-list mailing list