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-May/111625.html below:

storing reference counters outside of objects

[Python-Dev] CPython optimization: storing reference counters outside of objects [Python-Dev] CPython optimization: storing reference counters outside of objectsTerry Reedy tjreedy at udel.edu
Tue May 24 17:44:39 CEST 2011
On 5/24/2011 8:25 AM, Sturla Molden wrote:

> Artur Siekielski is not talking about cache locality, but copy-on-write
> fork on Linux et al.
>
> When reference counts are updated after forking, memory pages marked
> copy-on-write are copied if they store reference counts. And then he
> quickly runs out of memory. He wants to put reference counts and
> PyObjects in different pages, so only the pages with reference counts
> get copied.
>
> I don't think he cares about cache locality at all, but the rest of us
> do :-)

It seems clear that separating reference counts from objects satisfies a 
specialized need and should be done in a spedial, patched version of 
CPython rather than the general distribution.

-- 
Terry Jan Reedy

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