A RetroSearch Logo

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

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2017-January/147206.html below:

[Python-Dev] Investigating Python memory footprint of one real Web application

[Python-Dev] Investigating Python memory footprint of one real Web application [Python-Dev] Investigating Python memory footprint of one real Web applicationAntoine Pitrou solipsis at pitrou.net
Fri Jan 20 08:53:45 EST 2017
On Fri, 20 Jan 2017 22:30:16 +0900
INADA Naoki <songofacandy at gmail.com> wrote:
> >
> > Moving the refcount out of the PyObject will probably make increfs /
> > decrefs more costly, and there are a lot of them.  We'd have to see
> > actual measurements if a patch is written, but my intuition is that the
> > net result won't be positive.
> >
> > Regards
> >
> > Antoine.  
> 
> I agree with you.  But I have similar idea: split only PyGc_Head (3 words).

That sounds like an interesting idea.  Once an object is created, the
GC header is rarely accessed.  Since the GC header has a small constant
size, it would probably be easy to make its allocation very fast
(e.g. using a freelist).  Then the GC header is out of the way which
increases the cache efficiency of GC-tracked objects.

Regards

Antoine.
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