|
From: | Nicolas Hognon |
Subject: | Re: [Nel] NeL Network Engine |
Date: | Wed, 28 Feb 2001 15:10:53 +0100 |
User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; 0.8) Gecko/20010215 |
Looking at Apache or Samba projects, it seems that a good compromise is to set a 'maximum client requests by thread' and spawns threads accordingly. Apache uses process forking and memory sharing, but the design remains the same. You then just tune this max_request_by_thread for each OS, say 1 for Solaris which is said thread-efficient, 10 for Linux ? Just a hint ...
ok this is a solution but as i said in my last mail the problem is how managing more than one socket per thread efficiently ? under windows i know other solution than select / poll but under unixes i don't know other solutions. some one knows other one ? -- Nicolas Hognon address@hidden Virtools - The Behavior Company Tel. (+33) 1 42 71 46 86 / Fax. (+33) 1 42 71 86 53 http://www.virtools.com/
[Prev in Thread] | Current Thread | [Next in Thread] |