[Baypiggies] concurrency talk

[Guido van Rossum]

Possibly, but it *is* quite a change in topic. The discussions that
lead us here all got started by the desire to use multiple cores on a
single box, and the solutions suggested (from removing the GIL to
Erlang-style lightweight processes) are all geared towards that
scenario, and not towards distributed computing. The latter will
always scale to much larger jobs, but will also always be much more
painful to program.

On 9/17/07, Shannon -jj Behrens <jjinux at gmail.com> wrote:
> I think MapReduce should definitely be covered.  I think a lot more
> people are going to care about distributed computing than parallel
> computing.  At least, that's been my experience at my last three
> companies.
>
> -jj
>
> On 9/17/07, Guido van Rossum <guido at python.org> wrote:
> > I was thinking of E as well, but then I realized that E supports
> > *distributed* computing, which isn't quite the same field as
> > *parallel* computing. I'm not sure it's useful to increase the field
> > even more by adding distributed computing -- then you'd have to add
> > MapReduce and many other paradigms as well.
> >
> > On 9/17/07, jim stockford <jim at well.com> wrote:
> > >
> > >     maybe add E to the list (below Erlang)?
> > >
> > >     could the discussoin also include likely new CPU
> > > designs, PCB designs, embedded and desktop and
> > > server systems as well.
> > >
> > >
> > > On Sep 17, 2007, at 2:48 AM, Shannon -jj Behrens wrote:
> > >
> > > > Someone hinted at this idea earlier, but it might be fun to have an
> > > > overview discussion on a bunch of different concurrency techniques.
> > > > We could have a bunch of speakers, each speaking for 15 minutes on a
> > > > specific topic.  For instance:
> > > >
> > > > * Processes
> > > > * Threads (kernel and green)
> > > > * Parallel programming vs. distributed computing
> > > > * IO bound vs. CPU bound
> > > > * Asynchronous
> > > > * Twisted
> > > > * Stackless
> > > > * Actors
> > > > * Erlang
> > > >
> > > > We wouldn't actually try to cover how to use each of these.  Rather,
> > > > the goal would be to explain what it is and what are its advantages
> > > > and limitations.  That'd be a fun talk to give assuming we can keep it
> > > > shallow enough to cover everything but deep enough to make sense.
> > > >
> > > > Happy Hacking!
> > > > -jj
> > > >
> > > > --
> > > > http://jjinux.blogspot.com/
> > > > _______________________________________________
> > > > Baypiggies mailing list
> > > > Baypiggies at python.org
> > > > To change your subscription options or unsubscribe:
> > > > http://mail.python.org/mailman/listinfo/baypiggies
> > > >
> > >
> > > _______________________________________________
> > > Baypiggies mailing list
> > > Baypiggies at python.org
> > > To change your subscription options or unsubscribe:
> > > http://mail.python.org/mailman/listinfo/baypiggies
> > >
> >
> >
> > --
> > --Guido van Rossum (home page: http://www.python.org/~guido/)
> >
>
>
> --
> http://jjinux.blogspot.com/
>


-- 
--Guido van Rossum (home page: http://www.python.org/~guido/)