-
-
Notifications
You must be signed in to change notification settings - Fork 30.5k
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
GH-117759: Update GC docs for incremental collection #126695
GH-117759: Update GC docs for incremental collection #126695
Conversation
markshannon
commented
Nov 11, 2024
•
edited by bedevere-app
bot
Loading
edited by bedevere-app
bot
- Issue: Document the new incremental GC #117759
Co-authored-by: Daniel Hollas <[email protected]>
InternalDocs/garbage_collector.md
Outdated
generations. The main idea behind this concept is the assumption that most | ||
objects have a very short lifespan and can thus be collected soon after their | ||
creation. This has proven to be very close to the reality of many Python | ||
In order to limit the time each garbage collection takes, the GC implementation |
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.
In order to limit the time each garbage collection takes, the GC implementation | |
In order to bound the length of each garbage collection pause, the GC implementation |
InternalDocs/garbage_collector.md
Outdated
The time taken to scan the young generation can be controlled by controlling the | ||
size of the young, but the size of the old generation cannot be controlled. |
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.
The time taken to scan the young generation can be controlled by controlling the | |
size of the young, but the size of the old generation cannot be controlled. | |
The time taken to scan the young generation can be controlled by controlling its | |
size, but the size of the old generation cannot be controlled. |
InternalDocs/garbage_collector.md
Outdated
Each full scavenge is performed in a series of increments. | ||
For each full scavenge, the combined increments will cover the whole heap. | ||
|
||
For each increment, the portion of the heap scanned by a single collection is |
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.
what does "by a single collection" mean here?