[lkml]   [2003]   [Jan]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: debate on 700 threads vs asynchronous code
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


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:32    [W:0.030 / U:5.676 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site