Re: Parallelization on muli-CPU hardware?
From: Aahz (aahz_at_pythoncraft.com)
Date: 10/05/04
- Next message: Andrew Dalke: "Re: Retrieving the full path of Unix apps"
- Previous message: Josiah Carlson: "Re: New to Python: Features"
- In reply to: Andreas Kostyrka: "Re: Parallelization on muli-CPU hardware?"
- Next in thread: Daniel Dittmar: "Re: Parallelization on muli-CPU hardware?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 5 Oct 2004 17:07:12 -0400
In article <mailman.4377.1097009674.5135.python-list@python.org>,
Andreas Kostyrka <andreas@kostyrka.org> wrote:
>
>So, IMHO, there are basically the following design decisions:
>GIL: large granularity
>MSL: (many small locks) would slow down the overall execution of Python
> programs.
>MSLu: (many small locks, unsafe) inacceptable because it would change
> Python experience ;)
That's a good summation. Not quite QOTW, but definitely something
everyone should remember.
-- Aahz (aahz@pythoncraft.com) <*> http://www.pythoncraft.com/ WiFi is the SCSI of the 21st Century -- there are fundamental technical reasons for sacrificing a goat. (with no apologies to John Woods)
- Next message: Andrew Dalke: "Re: Retrieving the full path of Unix apps"
- Previous message: Josiah Carlson: "Re: New to Python: Features"
- In reply to: Andreas Kostyrka: "Re: Parallelization on muli-CPU hardware?"
- Next in thread: Daniel Dittmar: "Re: Parallelization on muli-CPU hardware?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|