🚀 go-pugleaf

Oliver Young wrote:

> 
> > How exactly do you plan to use the extra CPU time?
> I'm trying to send as much as it is possible e-mails per minute. I'd
> like to start more threads if there is a lot of free CPU time. I
> belive number of started threads is dependant of CPU power. Am I
> wrong?

Quite possibly; the optimum number of worker threads in such a system
will also be affected by contention for shared resources between
threads (i.e. how much time threads spend waiting for resources to
become available) and, in this case, the network.

How are these e-mails being sent? Are you performing mx lookups, or
just fowarding to an SMTP server? In the first case it makes some sense
to have multiple threads processing jobs, although the network and the
machine will still have an affect on how many it's worth having. In the
second case, everything's being pushed to a single socket anyway, so
network access (at least) will have to be single-threaded.


> > Surely if your other threads are busy enough they will
> > consume all available CPU.
> Yes, but I was thinking that I should start 5 threads on P II 450
> MHz, and 15 threads on P III 1,0 GHz, and 30 threads on P4 2,4 GHz.
> Am I wrong?

Depends what they're doing, whether they're all doing it at the same
time, etc etc.

There are no hard and fast numbers in concurrency requirements, even
for a given machine - it depends upon work load as well.

If you describe a bit more about your architecure (provided this isn't
spam software :) I'll try and make some more concrete reccomendations.