measure the relative cost (cpu/memory) for deep copies

[tkashem]

What happened?

the apiserver makes a deep copy of an object in several code sites while serving a request by using DeepCopyObject() function. We want to measure the relative cost (cpu/memory) for deep copies by using benchmark testing to better understand the impact.

Recently we have added a deep copy for this PR - #94986, knowing the relative cost would help us understand how much impact a new deep copy can incur.

[tkashem]

/sig api-machinery

cc @liggitt

[tkashem]

/assign

[fedebongio]

/cc @apelisse
not an urgent priority
/triage accepted

[MadhavJivrajani]

@tkashem are you working on this? If not, would you mind if I tried taking it up?

[tkashem]

sure, give it a try.

/assign @MadhavJivrajani

[NikhilSharmaWe]

@tkashem I have not worked on testing before, could you please guide me a little on how can I benchmark test the cluster or code for getting info about the relative cost (cpu/memory) for deep copies. By this I will gain some experience in testing space.

[MadhavJivrajani]

@NikhilSharmaWe 👋🏼
I'm currently working on this and will document everything on this issue if you'd like to follow along and pitch in with questions/feedback! :)

[NikhilSharmaWe]

@MadhavJivrajani that will be great.
Thank you.

[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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 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 rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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:

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

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

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active 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:

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

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

/close

Instructions 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/test-infra repository.