Invisible <voi### [at] devnull> wrote:
> PS. Oh, it says at the bottom. 1996. Yeah, fast-forward 14 years and see
> how "extremely rarely essential" it is to do multi-threading. ;-)

Aside from embarassingly parallel tasks like raytracing, most apps still are
essentially single threaded, apart perhaps from another thread for a database
connection and another for GUI events, no matter how many cores keep idle in
your new CPUs.  At least the OS can start processes in different ones...

Coarse grained multiprocessing as represented by threads does that:  its
complexity prevents developers from tapping all that multicore power.  Fine
grained parallelism implicitely implemented by compilers for any chance they see
fit should help there... but not for severely imperative code...

Post a reply to this message