DZ-Jay wrote:
Thanks, Wilfried. That's what I'm doing now. However, I'm doing it
from the end of the Execute() method of the worker thread, right
before
destroying the server, like this:
Procedure WorkerThread.Execute;
Begin
_InitializeSrv(); // create
Try
--- QUOTE: SZ
If you do not want the ability to use multi-cores for
communication threads,
then async is the way to go. But IMO, it is an ill
design since chipmakers
are talking about 64-core CPUs and 10Gbps networks.
--- END.
Thanks, SZ. At this point I'm not so much concerned
about complexity
On 10/11/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
--- QUOTE: Arno Garrels
This is untested code. Also FThreadList has to be
made public. Note that OnMessage would fire in
different thread contexts but a single handler for
all is fine. Hope this helps.
--- END.
I'll look into it.
Fastream Technologies wrote:
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.
Those numbers don't tell
