Skip to content

runtime: RSS regression in gopher-lua benchmark likely at https://go.dev/cl/658036 #73931

@mknyszek

Description

@mknyszek

https://perf.golang.org/dashboard/?benchmark=GopherLuaKNucleotide-16&unit=peak-RSS-bytes&repository=go&branch=master&platform=linux%2Famd64&days=30&end=2025-05-29T20%3A45

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.NeedsFixThe path to resolution is known, but the work has not been done.Performancecompiler/runtimeIssues 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 rc1release-blocker

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions