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.

Sign up for GitHub

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

Jump to bottom

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
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. release-blocker
Milestone
Go1.14

Comments

@ianlancetaylor
Copy link
Contributor

We've recently started seeing some failures of TestMemoryPhysicalUtilization.

CC @mknyszek

2019-11-08T18:00:54-a2cd2bd/linux-mips-rtrk
2019-11-08T23:22:06-11da2b2/linux-mips64le-rtrk
2019-11-11T17:53:51-70be481/linux-mips64-rtrk
2019-11-11T20:17:03-eb55a0c/windows-386-2008
2019-11-11T23:28:26-eb68c4a/plan9-arm
2019-11-12T01:09:31-0ee22d9/plan9-arm
2019-11-12T18:52:52-1fe33e3/illumos-amd64
2019-11-13T08:07:51-bf5f641/windows-386-2008
2019-11-13T14:18:45-c075115/plan9-arm
2019-11-13T18:03:37-e762378/linux-mips-rtrk
@ianlancetaylor ianlancetaylor added NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. release-blocker labels Nov 14, 2019
@ianlancetaylor ianlancetaylor added this to the Go1.14 milestone Nov 14, 2019
@mknyszek
Copy link
Contributor

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

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

@gopherbot
Copy link

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

@gopherbot
Copy link

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

@mknyszek
Copy link
Contributor

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.

@golang golang locked and limited conversation to collaborators Nov 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. release-blocker
Projects
None yet
Milestone
Go1.14
Development

No branches or pull requests
3 participants
@mknyszek @ianlancetaylor @gopherbot