Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #9618
| From | "Waldek M." <wm@localhost.localdomain> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Re: Python threading/multiprocessing issue. |
| Date | 2011-07-16 13:41 +0200 |
| Organization | Mojito.pl |
| Message-ID | <ate4d7wlcrvs$.dlg@localhost.localdomain> (permalink) |
| References | <SNT106-W28C92B220F97ABFE97E73CB1490@phx.gbl> <CAPTjJmoHWOgbt_cHwtbOm7w9Mz8uJGaK+tCfd54y-psxd-4A9w@mail.gmail.com> <mailman.1100.1310793326.1164.python-list@python.org> |
Dnia Fri, 15 Jul 2011 22:15:15 -0700, Dennis Lee Bieber napisał(a): > And (so far as I understand it) each process can claim its own CPU > core, whereas threads share the active core. I do not think so. AFAIK, threads may be distributed over differrent CPUs (just like in any other programming language), only because of GIL, you might not notice any performance improvement with that. Best regards, Waldek
Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: Python threading/multiprocessing issue. Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2011-07-15 22:15 -0700 Re: Python threading/multiprocessing issue. "Waldek M." <wm@localhost.localdomain> - 2011-07-16 13:41 +0200
csiph-web