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

Only run GC 3 times instead of 4 to scrub #350

Merged
merged 3 commits into from
Jan 4, 2024
Merged

Conversation

Zentrik
Copy link
Contributor

@Zentrik Zentrik commented Dec 31, 2023

Per slack, 'Diogo changed it so it only needs 3 to promote everything to old generation now'.

Per slack, 'Diogo changed it so it only needs 3 to promote everything to old generation now'.
@gdalle
Copy link
Collaborator

gdalle commented Jan 3, 2024

Diogo Netto liked the comment on Slack so I'll take that as a green flag. Have asked him for a review nonetheless to avoid screwing up

@ghost
Copy link

ghost commented Jan 3, 2024 via email

@gdalle
Copy link
Collaborator

gdalle commented Jan 3, 2024

Sorry I tagged the wrong Diogo Netto 🤣

@ghost
Copy link

ghost commented Jan 3, 2024 via email

Copy link

@d-netto d-netto left a comment

Choose a reason for hiding this comment

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

If the goal of gcscrub is to ensure all objects reach the oldest generation, then this PR conforms with the changes we introduced in the GC in v1.10.

Want to note that since you are relying on internal GC behavior here (which we're free to change in any version), then it might be a good idea to guard these changes under a version check: i.e. put a @static if VERSION=1.10 or alike.

@gdalle
Copy link
Collaborator

gdalle commented Jan 4, 2024

@Zentrik wanna add that to make sure that on <= 1.9 we do 4 sweeps and on >= 1.10 we do 3?

@gdalle gdalle merged commit 3742326 into JuliaCI:master Jan 4, 2024
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants