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.

Sign up for GitHub

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

Jump to bottom

run a stress test on prod #1353

Open
4 tasks
goern opened this issue Mar 30, 2021 · 13 comments
Open
4 tasks

run a stress test on prod #1353

goern opened this issue Mar 30, 2021 · 13 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@goern
Copy link
Member

goern commented Mar 30, 2021

As a Thoth Operator,
I want to run a stress test on User-API/advise
so that I can identify a break-even point for users/requests

Acceptance Criteria

  • create a test script to query user-api https://www.tornadoweb.org/en/stable/index.html
  • identify the number of user requests per minute that will be answered within 5min?
  • prove that user-api will not break -> always deliver 200
  • identify a threshold for a potential API throttling

References
@fridex
Copy link
Contributor

fridex commented Mar 31, 2021

tornado is a webserver, I couldn't recall siege. However there are other tools (probably better for this case):

https://github.com/denji/awesome-http-benchmark

@harshad16 harshad16 added the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label Apr 13, 2021
@goern
Copy link
Member Author

goern commented Jun 10, 2021

@harshad16 are you working on this?

/kind feature

@sesheta sesheta added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 10, 2021
@goern
Copy link
Member Author

goern commented Jun 10, 2021

@fridex is this soon'ish or longterm prio? thx!

@goern goern added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. labels Jun 10, 2021
@fridex
Copy link
Contributor

fridex commented Jun 10, 2021

@fridex is this soon'ish or longterm prio? thx!

As we are open to community and have also external consumers of the service, it would be good to have this in place to make sure users can consume recommendations and that we can reliably provide them.

@goern
Copy link
Member Author

goern commented Jun 10, 2021

/priority important-soon

@sesheta sesheta added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jun 10, 2021
@sesheta
Copy link
Member

sesheta commented Jul 16, 2021

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

@sesheta sesheta added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. labels Jul 16, 2021
@fridex
Copy link
Contributor

fridex commented Jul 16, 2021

/remove-lifecycle rotten

@sesheta sesheta removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jul 16, 2021
@sesheta
Copy link
Member

sesheta commented Aug 24, 2021

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

@sesheta sesheta closed this as completed Aug 24, 2021
@sesheta
Copy link
Member

sesheta commented Aug 24, 2021

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/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.

@fridex
Copy link
Contributor

fridex commented Aug 25, 2021

/triage accepted
/remove-lifecycle rotten
/reopen

@sesheta sesheta reopened this Aug 25, 2021
@sesheta
Copy link
Member

sesheta commented Aug 25, 2021

@fridex: Reopened this issue.

In response to this:

/triage accepted
/remove-lifecycle rotten
/reopen

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.

@sesheta sesheta added the triage/accepted Indicates an issue or PR is ready to be actively worked on. label Aug 25, 2021
@harshad16 harshad16 changed the title run a stress test on zero-prod run a stress test on prod Sep 14, 2021
@harshad16 harshad16 added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Sep 14, 2021
@goern
Copy link
Member Author

goern commented Jan 19, 2022

this issue doesnt seem to be important-soon, so I will
/priority important-longterm
/remove-priority important-soon

feel free to reraise the priority!

@sesheta sesheta added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Jan 19, 2022
@sesheta sesheta removed the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jan 19, 2022
@fridex fridex mentioned this issue Jan 26, 2022
Closed
@mayaCostantini
Copy link
Contributor

/assign @mayaCostantini

@codificat codificat mentioned this issue Mar 7, 2022
Closed
3 tasks
@harshad16 harshad16 added the sig/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps. label Apr 12, 2022
@mayaCostantini mayaCostantini removed their assignment Dec 1, 2022
@goern goern added priority/backlog Higher priority than priority/awaiting-more-evidence. and removed priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. labels Feb 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Planning Board
Status: Blocked
SIG-DevSecOps
Status: 📋 Backlog
Milestone
No milestone
Development

No branches or pull requests
5 participants
@goern @fridex @harshad16 @sesheta @mayaCostantini