David Hooker wrote:
>
> So instead of having 100 connections per thread, and then creating a
> new thread, and then
> another 100 connections, and so on... I want to have 4 threads and
> have (number of connections at this present moment) / 4 connections
> per thread.
I don't see the problem,
On 6/14/06, Francois Piette <[EMAIL PROTECTED]> wrote:
>
> >> OK, but what if I want one thread per CPU?
> >>
> >> So if I have a 4 CPU rig and 400 connections, I want to
> >> have 4 threads and 100 connections per thread.
> >> But if the load increases to 600 connections, I want to
> >> have 4 thr
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> On Behalf Of Francois Piette
>
> This si not a winsock or TCP/IP component issue. It is an OS issue. I
> don't know Windows has an API to force a thread to run on a given CPU.
SetThreadAffinityMask
> You have an API to know the number of proc
Suite, freeware)
Author of MidWare (Multi-tier framework, freeware)
http://www.overbyte.be
- Original Message -
From: "David Hooker" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, June 14, 2006 4:23 AM
Subject: [twsocket] ICS threaded server and load balancing
> &g
>From borland.public.delphi.internet.winsock:
Francois wrote:
> The server component will create a new thread as the previous one reached
> the maximum number of client you've setup. It is the OS which schedule the
> available CPUs to the threads in the ready state.
OK, but what if I want one
