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
With the introduction of PGO in #13884, the initial produced CPU profile files seem to be too large, see this pull request for example. This is caused by collecting 100% of the samples in apm-perf and excessive tagging during the benchmarking. Such large profile files are not very well suited to be stored under git. Therefore we should optimize apm-perf to only collect a limited profile sample instead and discard all unnecessary tagging to reduce the size.
The text was updated successfully, but these errors were encountered:
Description
With the introduction of PGO in #13884, the initial produced CPU profile files seem to be too large, see this pull request for example. This is caused by collecting 100% of the samples in apm-perf and excessive tagging during the benchmarking. Such large profile files are not very well suited to be stored under git. Therefore we should optimize apm-perf to only collect a limited profile sample instead and discard all unnecessary tagging to reduce the size.
The text was updated successfully, but these errors were encountered: