A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2011-August/112782.html below:

[Python-Dev] GIL removal question

[Python-Dev] GIL removal questionMaciej Fijalkowski fijall at gmail.com
Wed Aug 10 22:06:58 CEST 2011
On Wed, Aug 10, 2011 at 7:19 PM, Raymond Hettinger
<raymond.hettinger at gmail.com> wrote:
>
> On Aug 10, 2011, at 4:15 AM, Nick Coghlan wrote:
>
> After implementing the aforementioned step 5, you will find that the
> performance of everything, including the threaded code, will be quite a bit
> worse.  Frankly, this is probably the most significant obstacle to have any
> kind of GIL-less Python with reasonable performance.
>
> PyPy would actually make a significantly better basis for this kind of
> experimentation, since they *don't* use reference counting for their
> memory management.
>
> Jython may be a better choice.  It is all about concurrency.  Its dicts are
> built on top of Java's ConcurrentHashMap for example.
>

Jython is kind of boring choice because it does not have a GIL at all
(same as IronPython). It might *work* for what you're trying to
achieve but GIL-removal is not really that interesting.
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4