-
Notifications
You must be signed in to change notification settings - Fork 18.5k
Closed
Closed
Copy link
Labels
BugReportIssues describing a possible bug in the Go implementation.Issues describing a possible bug in the Go implementation.NeedsFixThe path to resolution is known, but the work has not been done.The path to resolution is known, but the work has not been done.Performancecompiler/runtimeIssues related to the Go compiler and/or runtime.Issues related to the Go compiler and/or runtime.okay-after-rc1Used by release team to mark a release-blocker issue as okay to resolve either before or after rc1Used by release team to mark a release-blocker issue as okay to resolve either before or after rc1release-blocker
Milestone
Description
I suspect this might be related to the fact that ptrBuf is created on each P, but isn't actually used if the green tea experiment is off. Or it's just something related to some new fixed-size overhead. We only see this regression in gopher-lua, which is one of the few small-heap benchmarks we track RSS for.
Metadata
Metadata
Assignees
Labels
BugReportIssues describing a possible bug in the Go implementation.Issues describing a possible bug in the Go implementation.NeedsFixThe path to resolution is known, but the work has not been done.The path to resolution is known, but the work has not been done.Performancecompiler/runtimeIssues related to the Go compiler and/or runtime.Issues related to the Go compiler and/or runtime.okay-after-rc1Used by release team to mark a release-blocker issue as okay to resolve either before or after rc1Used by release team to mark a release-blocker issue as okay to resolve either before or after rc1release-blocker