[Scons-dev] Multiprocessing instead of threads?
Russel Winder
russel at winder.org.uk
Tue Nov 24 13:41:23 EST 2015
On Mon, 2015-11-23 at 21:01 +0000, William Blevins wrote:
>
>
> Threads automatically benefit here as they are shared memory by
> default,
> but with extra work, we could also do shared memory with
> subprocesses.
In Go the aphorism is:
Don't communicate by sharing memory; share memory by communicating.
and this is very right, something that has been known since the 1960s.
Do not do shared memory multithreading and dealing with the fall-out
(*), have all threads be either in a thread pool handling independent
tasks or only have processes with no shared memory.
(*) The only caveat would be for some operating system implementation
situations.
--
Russel.
=============================================================================
Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.winder at ekiga.net
41 Buckmaster Road m: +44 7770 465 077 xmpp: russel at winder.org.uk
London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part
URL: <https://pairlist2.pair.net/pipermail/scons-dev/attachments/20151124/087153ef/attachment.pgp>
More information about the Scons-dev
mailing list