Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stress of registry-sandbox.k8s.io #16

Closed
ameukam opened this issue Feb 16, 2022 · 13 comments
Closed

Stress of registry-sandbox.k8s.io #16

ameukam opened this issue Feb 16, 2022 · 13 comments
Assignees
Labels
priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra.

Comments

@ameukam
Copy link
Member

ameukam commented Feb 16, 2022

oci-proxy is currently deployed over the 2 GCP regions: us-central1 and us-west1. We should do some stress tests to build confidence on what we are building and also ensure we can handle k8s.gcr.io traffic.

We should probably ask to GCR team some outdated metrics.

/sig k8s-infra
/priority important-longterm

@k8s-ci-robot k8s-ci-robot added sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Feb 16, 2022
@BenTheElder
Copy link
Member

/assign @BenTheElder @ameukam

@ameukam
Copy link
Member Author

ameukam commented Mar 16, 2022

/assign @BobyMCbobs

@k8s-ci-robot
Copy link
Contributor

@ameukam: GitHub didn't allow me to assign the following users: BobyMCbobs.

Note that only kubernetes-sigs members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @BobyMCbobs

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.

@BobyMCbobs
Copy link
Member

BobyMCbobs commented Mar 17, 2022

Background

image

Production Kubernetes artifacts currently serve ~60,000,000 requests every day.

Results

Ran some stress testing against the current registry.k8s.io and the results look pretty good.
The tests were not following redirection and only hitting https://registry.k8s.io/v2/

10,000 requests in 30s

image

10,000,000 requests in 30s

image

100,000,000 requests in 60s

image

Thoughts

Throughout the testing, the service was still accessible and did not appear to have any issues even at 100,000,000 requests per minute.
Given 100,000,000 per-minute running fine and Kubernetes artifacts receiving only 60,000,000 requests per-day, I think that it appears stable

@dims
Copy link
Member

dims commented Mar 17, 2022

that's great news @BobyMCbobs

@hh
Copy link
Member

hh commented Mar 17, 2022

Thanks @BobyMCbobs ! Great work!

@aojea
Copy link
Member

aojea commented Mar 17, 2022

impressive,

now, if we want to be paranoid https://groups.google.com/g/golang-nuts/c/MFZd6b8zQTQ/m/ISD96eyXtD4J 😄

@ameukam
Copy link
Member Author

ameukam commented Mar 23, 2022

@BobyMCbobs is it possible to disclose/document somewhere how this is was done ? (may be https://git.k8s.io/k8s.io/registry.k8s.io ?). Could be really useful if someone else want to re-do it.

@BobyMCbobs
Copy link
Member

@ameukam, of course. I'll get back to you on that

@riaankleinhans riaankleinhans moved this from Backlog to Breakdown Done in registry.k8s.io (SIG K8S Infra) Mar 29, 2022
@riaankleinhans riaankleinhans moved this from Breakdown Done to Implementation TODO in registry.k8s.io (SIG K8S Infra) Mar 29, 2022
@riaankleinhans riaankleinhans moved this from Implementation TODO to Implementation Done in registry.k8s.io (SIG K8S Infra) Mar 30, 2022
@BobyMCbobs
Copy link
Member

Stress test docs merged in kubernetes/k8s.io#3565

@riaankleinhans riaankleinhans moved this from Implementation Done to Validation TODO in registry.k8s.io (SIG K8S Infra) Mar 31, 2022
@hh
Copy link
Member

hh commented Mar 31, 2022

Do we want to stress test anymore or can we close this ticket.

@dims
Copy link
Member

dims commented Mar 31, 2022

@hh we can close this out

Repository owner moved this from Validation TODO to Breakdown Done in registry.k8s.io (SIG K8S Infra) Apr 1, 2022
@BenTheElder
Copy link
Member

Thanks folks!

@riaankleinhans riaankleinhans moved this from Breakdown Done to Implementation Done in registry.k8s.io (SIG K8S Infra) Apr 1, 2022
@hh hh moved this from Implementation Done to Validation TODO in registry.k8s.io (SIG K8S Infra) Apr 1, 2022
@hh hh moved this from Validation TODO to Validation Done in registry.k8s.io (SIG K8S Infra) Apr 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra.
Projects
Development

No branches or pull requests

7 participants