Alvin
Sat Aug 21 07:24:44 CDT 2004
That's my gripe with .net. They made it so easy to use threads, everybody is
doing it some without the slightest clue of what is going. at least in C++
it was difficult enough that it scared people away from using it so it was
left to those few people brave and knowledgable.
--
Regards,
Alvin Bruney
[ASP.NET MVP
http://mvp.support.microsoft.com/default.aspx]
Got tidbits? Get it here...
http://tinyurl.com/27cok
"David Levine" <noSpamdlevineNNTP2@wi.rr.com> wrote in message
news:edNs971hEHA.3348@TK2MSFTNGP12.phx.gbl...
> You are probably running out of virtual address space. .NET maps each
> thread
> to an underlying operating system thread, and allocates 1M of virtual
> address space for each one. By default each app gets a max of 2G of
> virtual
> address space from the operating system, so you are probably bumping into
> this limit.
>
> As others have mentioned, no one writes code that uses so many threads,
> most
> of which are blocked waiting on other operations to complete. Use a
> threadpool, either the .NET pool (recommended) or roll your own.
>
>
> "Parahat Melayev" <parahat@momenttech.com> wrote in message
> news:%23VGU17dhEHA.1888@TK2MSFTNGP10.phx.gbl...
>> Hi
>>
>> I am programming a multi-threaded asyncronous server with .NET
>>
>> But when systems thread count reaches to 1350 system can't respond.
>>
>> Simply my design is creating a Reading Thread after every Accept.
>> And creating a Writing Thread when server sends data.
>>
>> Can you share your experience with me on Network Programming and
>> Multi-Threading.
>>
>>
>
>