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

workaround upstream inlining issue #3

Merged

Conversation

felixge
Copy link
Member

@felixge felixge commented Apr 25, 2024

Work around golang issue 65532 by dropping samples belonging to the problematic gRPC function that causes significant memory increases when inlined.

@felixge felixge force-pushed the felix.geisendoerfer/PROF-9665-memory-increase-workaround branch from 2a69d9c to c3a1ae3 Compare April 25, 2024 13:59
@felixge felixge force-pushed the felix.geisendoerfer/PROF-9665-memory-increase-workaround branch from c3a1ae3 to 7b657f2 Compare April 25, 2024 14:05
@felixge felixge marked this pull request as ready for review April 25, 2024 14:05
Copy link

@nsrip-dd nsrip-dd left a comment

Choose a reason for hiding this comment

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

LGTM!

@felixge felixge merged commit 60fb0c2 into main Apr 25, 2024
2 checks passed
@felixge felixge deleted the felix.geisendoerfer/PROF-9665-memory-increase-workaround branch April 25, 2024 14:14
noinline.go Show resolved Hide resolved
felixge added a commit that referenced this pull request Jun 6, 2024
Removing the samples for functions that have known inlining issues skews
the PGO profile and might cause previously cold functions to be promoted
to hot functions.

It's probably not a big issue, but this is an easy improvement to make,
so why not.

Kudos to Michael Pratt for pointing this out pointing this out in
#3 (comment)
felixge added a commit that referenced this pull request Jun 6, 2024
Removing the samples for functions that have known inlining issues skews
the PGO profile and might cause previously cold functions to be promoted
to hot functions.

It's probably not a big issue, but this is an easy improvement to make,
so why not.

Kudos to Michael Pratt for pointing this out pointing this out in
#3 (comment)
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