[Chicago] Kickstarter Fund to get rid of the GIL

Alex Gaynor alex.gaynor at gmail.com
Sat Jul 23 20:11:33 CEST 2011


On Sat, Jul 23, 2011 at 10:58 AM, Joshua Herman <zitterbewegung at gmail.com>wrote:

> How about making all datastructures immutable and performing copies of
> each data structure instead of mutation? Its similar to what clojure
> and erlang does.
>
> On Sat, Jul 23, 2011 at 12:54 PM, Brian Ray <brianhray at gmail.com> wrote:
> > On Sat, Jul 23, 2011 at 12:37 PM, Alex Gaynor <alex.gaynor at gmail.com>
> wrote:
> >>
> >> "high performance just create multi processes that message" very rarely
> have
> >> I heard IPC and high performance in the same sentence.
> >> Alex
> >
> > Can you elaborate?  Taking full advantage of multiple processors could
> > increase performance, no?  I believe IPC was Guido's suggestion.
> >
> > IPC of some sort has already been pretty well established approach.
> >
> > --
> >
> > Brian Ray
> > _______________________________________________
> > Chicago mailing list
> > Chicago at python.org
> > http://mail.python.org/mailman/listinfo/chicago
> >
> _______________________________________________
> Chicago mailing list
> Chicago at python.org
> http://mail.python.org/mailman/listinfo/chicago
>

Making all datasructures immutable violates the constraint that existing
APIs can't be changed.  IPC carries a high overhead because a) you have to
serialize and deserialize all data structures, b) you can't really use it
with large datasets as you'll have multiple copies in each process.

Alex

-- 
"I disapprove of what you say, but I will defend to the death your right to
say it." -- Evelyn Beatrice Hall (summarizing Voltaire)
"The people's good is the highest law." -- Cicero
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/chicago/attachments/20110723/c922708a/attachment.html>


More information about the Chicago mailing list