S
Strobe
I'm definitely running several apps at once, which is what makes this
decision tricky
Note, it has to be apps that can use several cores at once.
Most older apps were written to run only on a single CPU - they just
don't have the first clue as to how to use any extra cores.
The current version of BOINC (the distributed processing manager) can allocate
separate tasks to as many cores as you want, and I believe newer Photoshops
will automatically shift some chores to your extra cores if they're idle.
Designing SW to split processing between cores isn't simple - the coder has to
make sure all the threads stay synchronised so that time isn't wasted waiting
for an errant sub-thread to finish. There was an early real-time multi-procesor
system that worked well (Sperry Scamp?) but had to spend a significant percent
of its time polling adjacent CPUs for new results.
I expect the most aggressive use of multiprocessing will - of course - be with
games.