You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great if the binaries were shipped with Profile-guided Optimization (PGO) enabled. PGO uses real usage data to optimize the code, making the binaries faster and more efficient, leading to noticeable performance improvements.
Describe the use case of the feature
By using profiling data from the profile-mem flag to generate a PGO file, we can potentially improve performance. This approach allows us to fine tune the engine based on actual memory usage, optimizing it for better efficiency during runtime.
Implementation details:
On push event:
Generate heap profile with profile-mem flag.
Create default.pgo PGO file from memory profile.
Push PGO file to pgo branch (dedicated).
Update the build command in .goreleaser.yml.
Describe alternatives you've considered
Instead of pushing the PGO file to the repo (3), an alternative could be storing the file as an artifact (actions/upload-artifact).
Describe your feature request
It would be great if the binaries were shipped with Profile-guided Optimization (PGO) enabled. PGO uses real usage data to optimize the code, making the binaries faster and more efficient, leading to noticeable performance improvements.
Describe the use case of the feature
By using profiling data from the
profile-mem
flag to generate a PGO file, we can potentially improve performance. This approach allows us to fine tune the engine based on actual memory usage, optimizing it for better efficiency during runtime.Implementation details:
On
push
event:profile-mem
flag.default.pgo
PGO file from memory profile.pgo
branch (dedicated)..goreleaser.yml
.Describe alternatives you've considered
Instead of pushing the PGO file to the repo (3), an alternative could be storing the file as an artifact (
actions/upload-artifact
).Additional context
https://go.dev/doc/pgo
Ex:
The text was updated successfully, but these errors were encountered: