Try doing that with threads.
Actually I would recommend the approach c)
c) Write an asynchronous system with only 2 or three threads where I
manage the connections and keep the state of each connection in a data
On fre, 2003-01-24 at 00:19, Lee Chin wrote:
> I am discussing with a few people on different approaches to solving a scale problem I am having, and have gotten vastly different views
> In a nutshell, as far as this debate is concerned, I can say I am writing a web server.
> Now, to cater to 700 clients, I can
> a) launch 700 threads that each block on I/O to disk and to the client (in reading and writing on the socket)
> b) Write an asycnhrounous system with only 2 or three threads where I manage the connections and stack (via setcontext swapcontext etc), which is progromatically a little harder
> Which way will yeild me better performance, considerng both approaches are implemented optimally?
Terje Eggestad mailto:firstname.lastname@example.org Scali Scalable Linux Systems http://www.scali.com
Olaf Helsets Vei 6 tel: +47 22 62 89 61 (OFFICE) P.O.Box 150, Oppsal +47 975 31 574 (MOBILE) N-0619 Oslo fax: +47 22 62 89 51 NORWAY _________________________________________________________________________
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/