SSA is very inefficient with huge number of labels/annotations/...

[wojtek-t]

As shown here:
https://github.com/kubernetes/kubernetes/pull/110569/files#diff-c9661ce6b32ebf6604536c747826c618fa7d057248f4dffe11d576063a3b480bR358-R363

SSA (computing ManagedFields) is highly inefficient for huge number of labels/annotations and with high enough numbers (the original test had 130,000 labels) could easily exceed 10s.
As pointed in the comment thread there, I don't perceive it as a top priority as it doesn't seem to be a usecase that is really used in production usecases, but it's probably worth discussing that explicitly and making a conscious decision.

/sig api-machinery
/priority important-longterm
/kind bug

@apelisse

@aojea - FYI

[ardaguclu]

/cc

[leilajal]

/cc @Jefftree @alexzielenski
/triage accepted

[apelisse]

We took a quick look at that, we know why it happens. The fix is not trivial, and while I wish fixing this would improve the overall performance, I don't know if it will be better for small maps/lists. We'll keep that in mind though, this is pretty terrible.

[wojtek-t]

@apelisse - thanks!
As I wrote above I don't think it's a top priority at this point, it's just a limitation we should keep in mind (and maybe worth documenting?)
If it's fixable then great, but if it would be in the cost of typical usecase, it may not be worth it.

[tkashem]

/cc

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[wojtek-t]

/remove-lifecycle stale

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[wojtek-t]

/triage accepted