Thanks for the replies.

Every process that I have examined in task manager has its affinity set only
CPU 0 and, since I have never (knowingly) altered the default behavior, this
might contradict your assertion.

I think I would be happy if the affinity of all processes were set to both
processors. This leaves me with two questions:
How can it be accomplished (i.e. restoring the default behavior)?
Is there a downside to having done this?

It would also be nice to know how the default behavior was altered so that,
in the future, I can avoid it happening again.


"Ian D" wrote:

>
> <sierrabravobravo@gmail.com> wrote in message
> news:4f42a868-d7fa-4447-904a-8bd9e0a65f51@34g2000hsh.googlegroups.com...
> >I am using an Intel core 2 duo processor.
> >
> > When I use the task manager to view the affinity of the number
> > processes it appears that all have only CPU 0 Checked. Further, when
> > I have two CPU intensive processes executing simultaneously there
> > seems to be very little activity on CPU 1 and CPU 0 is fully
> > saturated.
> >
> > I fear that there is some setting that enables the task scheduler use
> > both CPUs that is not set correctly. What, if anything, can I do to
> > get some sort load-balancing between the two processors?
>
> The task scheduler's job is to run applications at predetermined
> times. It has nothing to do with scheduling CPU affinity. Only
> XP/Vista and multithreaded software will make simultaneous use of
> both CPUs. However in Task Manager you can set the affinities
> of your two processes so that one will run on CPU1 and the other
> on CPU2. You will have to do this each time you start those
> processes. By default, applications have the affinity set to both
> CPUs. If the bar graph to the right of the individual CPU graphs
> goes beyond 50%, then both CPUs are being used.
>
>
>