Re: Parallelization on muli-CPU hardware?
From: Aahz (aahz_at_pythoncraft.com)
Date: 10/06/04
- Previous message: Aahz: "Re: Parallelization on muli-CPU hardware?"
- In reply to: Sam G.: "Re: Parallelization on muli-CPU hardware?"
- Next in thread: Aahz: "Re: Parallelization on muli-CPU hardware?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 6 Oct 2004 16:40:15 -0400
In article <ck0emf$1ar$1@s5.feed.news.oleane.net>,
Sam G. <nospam:samuelgay@yahoo.fr> wrote:
>
>But if only one thread per interpreter could run at a time, in multicore
>two (or more) thread can't run at the same time. In performance the
>result is almost the same : if the server has nothing else than running
>python (not real i know, just to be simple), only one core work...
>
>Not very good for Zope, as multicore are for the near future...
Depends where it bogs down. If it's CPU, it may be an issue. If it's
I/O, CPython already releases the GIL and Zope benefits.
-- 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)
- Previous message: Aahz: "Re: Parallelization on muli-CPU hardware?"
- In reply to: Sam G.: "Re: Parallelization on muli-CPU hardware?"
- Next in thread: Aahz: "Re: Parallelization on muli-CPU hardware?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]