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

Provide automated load testing to benchmark performance of intercepting #447

Open
tomkerkhove opened this issue May 11, 2022 · 7 comments
Open

Provide automated load testing to benchmark performance of intercepting #447

tomkerkhove opened this issue May 11, 2022 · 7 comments
Labels
help wanted Extra attention is needed stale-bot-ignore All issues that should not be automatically closed by our stale bot

Comments

@tomkerkhove
Copy link
Member

Provide automated load testing to benchmark performance of intercepting.

We can use Artillery, Azure Load Testing, etc.
@isugimpy
Copy link

Very much interested to know more about the performance of this component. Seems like it has potential, but also could very easily be a bottleneck at scale.

@stale
Copy link

stale bot commented Aug 9, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale All issues that are marked as stale due to inactivity label Aug 9, 2022
@tomkerkhove tomkerkhove removed the stale All issues that are marked as stale due to inactivity label Aug 10, 2022
@v-shenoy v-shenoy self-assigned this Aug 16, 2022
@stale
Copy link

stale bot commented Oct 15, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale All issues that are marked as stale due to inactivity label Oct 15, 2022
@tomkerkhove tomkerkhove removed the stale All issues that are marked as stale due to inactivity label Oct 15, 2022
@v-shenoy v-shenoy removed their assignment Nov 22, 2022
@stale
Copy link

stale bot commented Jan 22, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale All issues that are marked as stale due to inactivity label Jan 22, 2023
@stale
Copy link

stale bot commented Jan 29, 2023

This issue has been automatically closed due to inactivity.

@stale stale bot closed this as completed Jan 29, 2023
@tomkerkhove tomkerkhove reopened this Jan 29, 2023
@stale stale bot removed the stale All issues that are marked as stale due to inactivity label Jan 29, 2023
@stale
Copy link

stale bot commented Mar 30, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale All issues that are marked as stale due to inactivity label Mar 30, 2023
@stale
Copy link

stale bot commented Apr 7, 2023

This issue has been automatically closed due to inactivity.

@stale stale bot closed this as completed Apr 7, 2023
@tomkerkhove tomkerkhove reopened this Apr 8, 2023
@stale stale bot removed the stale All issues that are marked as stale due to inactivity label Apr 8, 2023
@tomkerkhove tomkerkhove added the stale-bot-ignore All issues that should not be automatically closed by our stale bot label Apr 8, 2023
@JorTurFer JorTurFer added the help wanted Extra attention is needed label Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted Extra attention is needed stale-bot-ignore All issues that should not be automatically closed by our stale bot
Projects
Roadmap - KEDA HTTP Add-On
Status: To Do
Milestone
No milestone
Development

No branches or pull requests
4 participants
@tomkerkhove @isugimpy @JorTurFer @v-shenoy