🚀 go-pugleaf

"Remy Lebeau (TeamB)" <gambit47@yahoo.com> wrote in message
news:3e6e2fb9@newsgroups.borland.com...
>
> "Ted Tripp" <ttripp@skypoint.com> wrote in message
> news:3e6deb3f@newsgroups.borland.com...
> > The BCB5 manual recommends no more than 16 threads
> > per processor.
>
> Ignore it.  It's rubbish.  I've seen programs running hundreds of threads
at
> a time without any problems.
>
> > my app usually runs the CPU at about 100%, is there a
> > way to control that?
>
> That is typically caused by your code running tight loops that don't yield
> control to other threads/processes.  Try introducing Sleep() calls in your
> loops.

Of course, only one thread at a time is actually executing at any given
moment (one thread per processor).  It is also possible that having too many
(active) threads can have potentially devestating effects on performance due
to the overhead required to perform a context switch.  I seem to recall
reading something once which talked about the optimum number of simultaneous
threads per processor being somewhere around 3 or 4.  Less than that, and
you are wasting processor time (assuming the threads go to sleep once in a
while); more than that, and your process actually begins to slow down (if
all of the threads are active at the same time) because of context
switching.

I'll have to try to find where I read that...or perhaps someone else
remembers the same article(?) and knows where it is.  WDJ?  CUJ?

- Dennis