[Mono-dev] System.Runtime.Remoting.Channels.Tcp upgrade to Async

pablosantosluac at terra.es pablosantosluac at terra.es
Fri Feb 24 15:44:37 UTC 2012

I'm thinking on a slightly modified version since the pure async one
wasn't able to improve perf. under heavy load.

We're currently trying on EC2 with 500 concurrent version control
clients against a single Plastic SCM server, and reducing thread count
and such will help :)

On 23/02/2012 16:00, Robert Jordan wrote:
> Hi Pablo,
> On 23.02.2012 14:17, pablosantosluac at terra.es wrote:
>> Hi there,
>> As far as I see here:
>> https://github.com/mono/mono/tree/master/mcs/class/System.Runtime.Remoting/System.Runtime.Remoting.Channels.Tcp
>> the good old TCP channel has been largely untouched for about 4 years
>> now.
>> We use it on a daily basis in Plastic SCM (with some tweaks) but I
>> wonder if there's interest in converting it into Async sockets.
>> We're considering it right now, but my question is also: do you think
>> remoting is dead and should stay this way? Any better alternative?
> Remoting won't die anytime soon because it's a core part of the
> AppDomain machinery (I'm still using it in new projects whenever
> cross-framework compatibility isn't necessary and where security
> can be handled by another layer).
> About yours (or Dick Porter's?) Async patch: The problem is there
> aren't any Remoting maintainers left. I did it in the past
> (mostly bug fixing), but I'm starting to forget about the details ;)
> If you want this patch in Mono, you'd have to maintain at least
> the TcpChannel (monitoring Bugzilla, etc.).
> OTOH, given how plugable Remoting is, it would be easier to maintain
> your own AsycTcpChannel instead of risking a maintenance burden...
> Robert
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list

More information about the Mono-devel-list mailing list