Skip to content

Measure overhead of Request Queuing middleware in Plaintext benchmark #10704

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

Open
analogrelay opened this issue May 31, 2019 · 2 comments
Open
Labels
area-middleware Includes: URL rewrite, redirect, response cache/compression, session, and other general middlewares
Milestone

Comments

@analogrelay
Copy link
Contributor

Epic #10702

We should measure the impact of the Request Queuing middleware in the Plaintext benchmark. We may need to tune the queue depth and concurrent request limit numbers as part of this.

@analogrelay
Copy link
Contributor Author

FYI @sebastienros (just a heads-up that @DylanDmitri may be coming your way to find out a bit more about our benchmarks later on)

@sebastienros
Copy link
Member

I think I mentioned benchmarking to him, but didn't realize he had no idea what we can do already ;)

@analogrelay analogrelay added this to the 3.1.0 milestone Jun 18, 2019
@analogrelay analogrelay modified the milestones: 3.1.0, Backlog Nov 6, 2019
@amcasey amcasey added area-middleware Includes: URL rewrite, redirect, response cache/compression, session, and other general middlewares and removed area-runtime labels Jun 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-middleware Includes: URL rewrite, redirect, response cache/compression, session, and other general middlewares
Projects
None yet
Development

No branches or pull requests

5 participants