[Mono-dev] Memory usage on Mono remoting

[pablosantosluac at terra.es]

Thanks Robert,

So:

I'll modify the TcpChannel to use ThreadPool at System.Threading instead
of the built-in one.



Robert Jordan wrote:
> pablosantosluac at terra.es wrote:
>   
>> Also, you mentioned in a previous email that the TcpChannel should be
>> changed so it uses Asynch sockets. I've seen you use AsyncCallBack on XSP.
>>
>> My question is: I guess AsynchCallback will use a thread underneath,
>> won't it? If so: what's the advantage over launching threads to accept
>> calls?
>>     
>
> The thread pool threads are already launched and they are
> maintained by the runtime which is known to be faster than a
> managed thread pool implementation.
>
> Additionally, the default thread pool is already configurable
> (see mono(1)).
>
>   
>> You mentioned it is better to use the default ThreadPool instead of the
>> internal one in the TcpChannel, why is it going to be better?
>>     
>
> See above.
>
> Robert
>
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
>