"Chris Mullins" <cmull***@yahoo.com> wrote in message
news:%23rrCqdXpGHA.4268@TK2MSFTNGP04.phx.gbl...
> One of the things I've spent the last several years working on is a highly
> scalable socket server written in C#.
>
> The SoapBox Server has recently been tested to well over 100k simultanous
> users. This means it's handling 100k TCP connections on a Windows Platform
> without any trouble at all.
>
> I finally got around to writing a blog post that describes the different
> architectures we've gone through, and the pros and cons of each. All of
> these architectures scale fairly well, but there have been some surprising
> results. These architectures have included using the system threadpool,
> managing our own thread pool, doing work on the IOCP threads, and a few
> other things thrown in for good luck.
>
> I've seen so many people asking for guidance in this area, and I hope this
> serves people as a good starting point.
>
> http://makeashorterlink.com/?R2EE5246D
>
> All feedback is welcome, either here or on the blog...
>
> --
> Chris Mullins
> Coversant, Inc.
>
>

> One of the things I've spent the last several years working on is a
> highly scalable socket server written in C#.
>
> The SoapBox Server has recently been tested to well over 100k
> simultanous users. This means it's handling 100k TCP connections on a
> Windows Platform without any trouble at all.
>
> I finally got around to writing a blog post that describes the
> different architectures we've gone through, and the pros and cons of
> each. All of these architectures scale fairly well, but there have
> been some surprising results. These architectures have included using
> the system threadpool, managing our own thread pool, doing work on
> the IOCP threads, and a few other things thrown in for good luck.
>
> I've seen so many people asking for guidance in this area, and I hope
> this serves people as a good starting point.
>
> http://makeashorterlink.com/?R2EE5246D
>
> All feedback is welcome, either here or on the blog...

> "Jon Skeet [C# MVP]" <sk***@pobox.com> wrote
>>
>> If you have the time to run the tests with my "feature-rich" locks,
>> I'd be really interested in seeing the results. See
>> http://www.pobox.com/~skeet/csharp/miscutil/usage/locking.html for
>> usage, download link etc.
>>
>
> I recently (just this week) took a long and deep look through Jeff
> Richters "Power Threading" library. It's online at:
> http://www.wintellect.com/Resources.aspx
> (signing up for an account is free, then you can download the source).
>
> As somebody who takes quite a bit of pride in my knowledge of
> multi-threaded code, I have to say I was humbled.
>
> I learned more about locking in 4 hours this past tuesday evening
> than I've leared in a long, long time - possibly ever. Some of his
> source code commends were... eye opening.
> // NOTE: Just reading here (as compared to repeatedly calling
> Exchange) // improves performance because writing forces all CPUs to
> update this value
> // Don't do variable = value because reordered by compiler and/or CPU
>
> There was stuff like this throughout - as well as stuff that I wish I
> could wrap my head arond.
>
> I quite liked his abstract ResourceLock implementation, and the
> concrete variations on it.
>
> Unfortunatly I can't use this library, as the licensing of it
> prevents it from being run with Mono. I'll have to send him an email
> and see if I can get a relaxed license version.