-
-
Notifications
You must be signed in to change notification settings - Fork 33.2k
GH-127010: Don't lazily track and untrack dicts #127027
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 2 commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -532,8 +532,8 @@ of `PyGC_Head` discussed in the `Memory layout and object structure`_ section: | |
currently in. Instead, when that's needed, ad hoc tricks (like the | ||
`NEXT_MASK_UNREACHABLE` flag) are employed. | ||
|
||
Optimization: delay tracking containers | ||
======================================= | ||
Optimization: delayed untracking containers | ||
=========================================== | ||
|
||
Certain types of containers cannot participate in a reference cycle, and so do | ||
not need to be tracked by the garbage collector. Untracking these objects | ||
|
@@ -548,8 +548,8 @@ a container: | |
As a general rule, instances of atomic types aren't tracked and instances of | ||
non-atomic types (containers, user-defined objects...) are. However, some | ||
type-specific optimizations can be present in order to suppress the garbage | ||
collector footprint of simple instances. Some examples of native types that | ||
benefit from delayed tracking: | ||
collector footprint of simple instances. Historically, both dictionaries and | ||
tuples were untracked during garbage collection. Now it is only tuples: | ||
|
||
- Tuples containing only immutable objects (integers, strings etc, | ||
and recursively, tuples of immutable objects) do not need to be tracked. The | ||
|
@@ -561,12 +561,6 @@ benefit from delayed tracking: | |
already not tracked. Tuples are examined for untracking in all garbage collection | ||
cycles. It may take more than one cycle to untrack a tuple. | ||
|
||
- Dictionaries containing only immutable objects also do not need to be tracked. | ||
Dictionaries are untracked when created. If a tracked item is inserted into a | ||
dictionary (either as a key or value), the dictionary becomes tracked. During a | ||
full garbage collection (all generations), the collector will untrack any dictionaries | ||
whose contents are not tracked. | ||
|
||
The garbage collector module provides the Python function `is_tracked(obj)`, which returns | ||
the current tracking status of the object. Subsequent garbage collections may change the | ||
tracking status of the object. | ||
|
@@ -581,8 +575,6 @@ tracking status of the object. | |
>>> gc.is_tracked({}) | ||
False | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is empty dict still untracked? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. No it is tracked. I'll update the docs. |
||
>>> gc.is_tracked({"a": 1}) | ||
False | ||
>>> gc.is_tracked({"a": []}) | ||
True | ||
``` | ||
|
||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
4 changes: 4 additions & 0 deletions
4
Misc/NEWS.d/next/Core_and_Builtins/2024-11-19-17-17-32.gh-issue-127010.9Cl4bb.rst
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
Simplify GC tracking of dictionaries. All dictionaries are tracked when | ||
created, rather than being lazily tracked when a trackable object was added | ||
to them. This simplifies the code considerably and results in a slight | ||
speedup. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is now a single-item bullet list.