[EMAIL PROTECTED] wrote: > Hello: > Although impressive, that type of performance is > out of the scope of my application, which won't be > handling more than 100 (but mostly dozens) > connections at a time. I guess TWSocketServer is the > way to go for me.
Yes I think so. You only must ensure that lengthy, blocking tasks are moved into worker threads in order to not slow down response time to all other clients too much or not to block subsequent connection attempts. -- Arno Garrels [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html > > >> ------- Original Message ------- >>> From : Fastream > Technologies[mailto:[EMAIL PROTECTED] >> Sent : 10/11/2007 10:08:16 AM >> To : firstname.lastname@example.org >> Cc : >> Subject : RE: Re: [twsocket] TWSocketThrdServer friendly notice >> whendisconnecting. >> > >I test my ICS-based MT proxy with 20k connections > on our dual-core system. > It performs 2GBps, local-to-local. So that's one CPU > performance basically > since the tester also uses CPU! I would not imagine > such performance with > single thread. > > Best Regards, > > SZ -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be