-
Notifications
You must be signed in to change notification settings - Fork 76
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
Comments
/assign @BenTheElder @ameukam |
/assign @BobyMCbobs |
@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. In response to this:
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. |
BackgroundProduction Kubernetes artifacts currently serve ~60,000,000 requests every day. ResultsRan some stress testing against the current registry.k8s.io and the results look pretty good. 10,000 requests in 30s10,000,000 requests in 30s100,000,000 requests in 60sThoughtsThroughout the testing, the service was still accessible and did not appear to have any issues even at 100,000,000 requests per minute. |
that's great news @BobyMCbobs |
Thanks @BobyMCbobs ! Great work! |
impressive, now, if we want to be paranoid https://groups.google.com/g/golang-nuts/c/MFZd6b8zQTQ/m/ISD96eyXtD4J 😄 |
@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. |
@ameukam, of course. I'll get back to you on that |
Stress test docs merged in kubernetes/k8s.io#3565 |
Do we want to stress test anymore or can we close this ticket. |
@hh we can close this out |
Thanks folks! |
oci-proxy is currently deployed over the 2 GCP regions:
us-central1
andus-west1
. We should do some stress tests to build confidence on what we are building and also ensure we can handlek8s.gcr.io
traffic.We should probably ask to GCR team some outdated metrics.
/sig k8s-infra
/priority important-longterm
The text was updated successfully, but these errors were encountered: