|
Boost : |
From: Felipe Magno de Almeida (felipe.m.almeida_at_[hidden])
Date: 2005-08-03 22:47:56
On 8/3/05, Pedro Lamarão <pedro.lamarao_at_[hidden]> wrote:
> I must be absolutely ignorant in what constitutes a performant
> networking application, if multiple threads blocking on IO is a design
> doomed to general non-use by those writing multi-session applications.
>
> Can you explain to me what is fundamentally wrong with this model, and
> how the use of asynchronous primitives or the non-blocking mode is so
> vastly superior?
Asynchronous scales a lot better, if you're putting each session on a
thread it wont be able to handle too many connections reliably. With
asynchronous, completion ports or select/poll you're able to handle
multi-session without requiring more threads. That way you can have
one thread per processor and that way not kill the performance with
context switches.
>
> I would sincerely like to know, because I've been writing those for some
> time, and, though our clients aren't complaining, perhaps I could be
> delivering more.
Probably your application doesnt have to handle too many connections
at the same time.
>
> --
> Pedro Lamarão
>
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
-- Felipe Magno de Almeida Developer from synergy and Computer Science student from State University of Campinas(UNICAMP). Unicamp: http://www.ic.unicamp.br Synergy: http://www.synergy.com.br "There is no dark side of the moon really. Matter of fact it's all dark."
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk