Skip to content
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

Merged
merged 5 commits into from
Nov 14, 2024

Conversation

markshannon
Copy link
Member

@markshannon markshannon commented Nov 11, 2024

@markshannon markshannon changed the title Update GC docs GH-117759: Update GC docs for incremental collection Nov 11, 2024
@bedevere-app bedevere-app bot mentioned this pull request Nov 11, 2024
3 tasks
@markshannon markshannon marked this pull request as ready for review November 11, 2024 18:24
InternalDocs/garbage_collector.md Outdated Show resolved Hide resolved
InternalDocs/garbage_collector.md Outdated Show resolved Hide resolved
InternalDocs/garbage_collector.md Outdated Show resolved Hide resolved
InternalDocs/garbage_collector.md Outdated Show resolved Hide resolved
InternalDocs/garbage_collector.md Outdated Show resolved Hide resolved
InternalDocs/garbage_collector.md Show resolved Hide resolved
InternalDocs/garbage_collector.md Outdated Show resolved Hide resolved
InternalDocs/garbage_collector.md Outdated Show resolved Hide resolved
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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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 Show resolved Hide resolved
InternalDocs/garbage_collector.md Outdated Show resolved Hide resolved
InternalDocs/garbage_collector.md Outdated Show resolved Hide resolved
Comment on lines 369 to 370
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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.

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
Copy link
Member

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?

@markshannon markshannon merged commit 3966d8d into python:main Nov 14, 2024
27 checks passed
@markshannon markshannon deleted the update-gc-internal-docs branch November 18, 2024 14:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants