Re: debate on 700 threads vs asynchronous code

Corey Minyard
2003-01-24T22:43:47Z

Mark Mielke wrote:

>>And, for what it's worth, programmer productivity is sometimes
>>more important than all the above. I happen to work
>>at a place where performance is worth a lot of extra effort,
>>but other shops prefer to throw hardware at the problem and
>>not worry about that last 10%.
>>
>>
>
>Definately an argument for the one thread per connection model. :-)
>
I would disagree. One thread per connection is easier to conceptually
understand. In my experience, an event-driven model (which is what you
end up with if you use one or a few threads) is actually easier to
correctly implement and it tends to make your code more modular and
portable.

-Corey