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

runtime: TestPhysicalMemoryUtilization failures #35580

Closed
ianlancetaylor opened this issue Nov 14, 2019 · 5 comments
Closed

runtime: TestPhysicalMemoryUtilization failures #35580

ianlancetaylor opened this issue Nov 14, 2019 · 5 comments
Assignees
Milestone

Comments

@mknyszek

This comment has been minimized.

Copy link
Contributor

@mknyszek mknyszek commented Nov 14, 2019

I suspect the problem here is that the scavenger's scavAddr may already be too low (for some reason, and only by a little bit) to adequately achieve the desired physical memory utilization. I have some ideas on how to fix it and will come back to this bug shortly.

@mknyszek mknyszek self-assigned this Nov 14, 2019
@gopherbot

This comment has been minimized.

Copy link

@gopherbot gopherbot commented Nov 19, 2019

Change https://golang.org/cl/207999 mentions this issue: runtime: make the scavenger loop around the address space

@gopherbot

This comment has been minimized.

Copy link

@gopherbot gopherbot commented Nov 19, 2019

Change https://golang.org/cl/207998 mentions this issue: runtime: wake scavenger and update address on sweep done

@gopherbot

This comment has been minimized.

Copy link

@gopherbot gopherbot commented Nov 21, 2019

Change https://golang.org/cl/208377 mentions this issue: runtime: increase TestPhysicalMemoryUtilization threshold

@mknyszek

This comment has been minimized.

Copy link
Contributor

@mknyszek mknyszek commented Nov 21, 2019

Found the problem. It's that the page cache was hiding memory from the scavenger (which is intentional). Just uploaded a fix to the test to account for that.

@gopherbot gopherbot closed this in 1c5bd34 Nov 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.