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

Showing content from https://mail.python.org/pipermail/python-dev/2002-May/023985.html below:

[Python-Dev] Lazily GC tracking tuples

• Previous message: [Python-Dev] Lazily GC tracking tuples
• Next message: [Python-Dev] Lazily GC tracking tuples
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

I'm not sure I like this approach.  Slowing down PyTuple_SET_ITEM to
optimize a micro-benchmark seems dubious.  However, dropping the number
of tracked objects by 50% _does_ seem worthwhile.  Couldn't we get the
same effect by checking and untracking the appropriate tuples after
finishing a gen1 collection?  Each tuple would be checked once and short
lived tuples will probably not be checked at all.

  Neil

• Previous message: [Python-Dev] Lazily GC tracking tuples
• Next message: [Python-Dev] Lazily GC tracking tuples
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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