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/2008-June/080655.html below:

[Python-Dev] C API for gc.enable() and gc.disable()

[Python-Dev] C API for gc.enable() and gc.disable() [Python-Dev] C API for gc.enable() and gc.disable()Alexandre Vassalotti alexandre at peadrop.com
Thu Jun 26 01:35:15 CEST 2008
On Wed, Jun 25, 2008 at 4:55 PM, "Martin v. Löwis" <martin at v.loewis.de> wrote:
> I think exactly the other way 'round. The timing of thing should not
> matter at all, only the exact sequence of allocations and deallocations.

I would it be possible, if not a good idea, to only track object
deallocations as the GC traversal trigger? As far as I know, dangling
cyclic references cannot be formed when allocating objects. So, this
could potentially mitigate the quadratic behavior during allocation
bursts.

-- Alexandre
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