Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed4.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Return-Path: <python-python-list@m.gmane.org>
X-Original-To: python-list@python.org
Delivered-To: python-list@mail.python.org
X-Spam-Status: OK 0.005
X-Spam-Evidence: '*H*': 0.99; '*S*': 0.00; 'interpreter': 0.05; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'subject:skip:f 10': 0.09; 'subject:still': 0.09; 'suggest': 0.14; '"new': 0.16; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'threads.': 0.16; 'url:dabeaz': 0.16; 'fix': 0.17; 'wrote:': 0.18; 'hack': 0.22; 'header:User-Agent:1': 0.23; "aren't": 0.24; 'header:X-Complaints-To:1': 0.27; 'room': 0.29; "d'aprano": 0.31; 'overhead': 0.31; 'steven': 0.31; 'url:python': 0.33; 'programmers': 0.33; 'something': 0.35; 'but': 0.35; 'there': 0.35; "didn't": 0.36; 'responsible': 0.36; 'subject:?': 0.36; 'performance': 0.37; 'improving': 0.38; 'to:addr:python-list': 0.38; 'fact': 0.38; 'subject:" ': 0.39; 'to:addr:python.org': 0.39; 'received:org': 0.40; 'url:pdf': 0.68; 'horrible': 0.84; 'subject:High': 0.84; 'problems?': 0.91
X-Injected-Via-Gmane: http://gmane.org/
To: python-list@python.org
From: Sturla Molden <sturla.molden@gmail.com>
Subject: Re: "High water" Memory fragmentation still a thing?
Date: Sat, 4 Oct 2014 17:51:28 +0000 (UTC)
References: <542f8a27$0$12998$c3e8da3$5496439d@news.astraweb.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Gmane-NNTP-Posting-Host: 185-67-11.connect.netcom.no
User-Agent: NewsTap/4.0.1 (iPad)
X-: 
X-BeenThere: python-list@python.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe: <https://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive: <http://mail.python.org/pipermail/python-list/>
List-Post: <mailto:python-list@python.org>
List-Help: <mailto:python-list-request@python.org?subject=help>
List-Subscribe: <https://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups: comp.lang.python
Message-ID: <mailman.14603.1412445100.18130.python-list@python.org>
Lines: 19
NNTP-Posting-Host: 2001:888:2000:d::a6
X-Trace: 1412445101 news.xs4all.nl 2834 [2001:888:2000:d::a6]:39605
X-Complaints-To: abuse@xs4all.nl
Xref: csiph.com comp.lang.python:78701

Steven D'Aprano <steve+comp.lang.python@pearwood.info> wrote:

> [Aside: The thing that people fail to understand is that the GIL is not in
> fact something which *prevents* multi-tasking, but it *enables* cooperative
> multi-tasking:
> 
> http://www.dabeaz.com/python/GIL.pdf
> 
> although that's not to say that there aren't some horrible performance
> characteristics of the GIL. David Beazley has identified issues with the
> GIL which suggest room for improving the GIL and avoiding "GIL battles"
> which are responsible for much of the overhead of CPU-bound threads. Any C
> programmers who want to hack on the interpreter core?]

Didn't the "new GIL" fix some of these problems?


Sturla