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

Why not use wrk2? #7140

Open
enghitalo opened this issue Jan 15, 2024 · 4 comments
Open

Why not use wrk2? #7140

enghitalo opened this issue Jan 15, 2024 · 4 comments

Comments

@enghitalo
Copy link
Contributor

https://github.com/giltene/wrk2
or
https://github.com/mcollina/autocannon
or
https://github.com/codesenberg/bombardier
or
https://github.com/rogerwelin/cassowary (more resourses)

@waghanza
Copy link
Collaborator

I'd prefer to use https://github.com/lnx-search/rewrk (I plan to do a big refactor for that), but I have no bandwidth for this now

@cyrusmsk
Copy link
Contributor

I found also interesting tool oha..
Have no idea why there are so many different tools… that are doing pretty much the same thing..
https://github.com/denji/awesome-http-benchmark

btw how is refactoring is going?

@waghanza
Copy link
Collaborator

I still hesitate between

  • rewrk
  • goose
  • oha

In the list above

Any ideas ?

@cyrusmsk
Copy link
Contributor

I think for the first step it could be anything that is better than original wrk and which is easier to deploy. After that some other tools with extra capabilities could be considered.
For rich testing (not only simple query, but different inputs, randomized parameters, etc)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants