🌱 Avoid unnecessary memory allocation in ssa.Patch after cache hit - #14085
🌱 Avoid unnecessary memory allocation in ssa.Patch after cache hit#14085sbueringer wants to merge 2 commits into
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@sbueringer: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
/hold until #13803 is merged |
What this PR does / why we need it:
Around 4-5% of our memory allocation in core CAPI at stable state is just updating modified after a cache hit in ssa.Patch. We don't need that as we never read the updatedObject after ssa.Patch
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Part of #13305