Vegeta VS website

Vegeta worth a look if you want something a bit more sophisticated: https://github.com/tsenart/vegeta

There are tons of tools to do this, I'll use Vegeta

To install vegeta, grab the right download url from https://github.com/tsenart/vegeta/releases/tag/v12.11.1 and download using the below command.

One of the easiest ways to send lots of fabricated requests at the same time is to use the Vegeta load testing tool. Being a load testing tool, it can send lots of requests consistently, every second, to the given target URL. You can read more about Vegeta on GitHub. The binary can be downloaded and used without installation.

Good morning what tool do you use to test your infra in terms of http load ? A tool that works, I tested : - https://github.com/tsenart/vegeta but it returns 0 errors or a http_net error from Golang - LOIC (Low Orbit Ion Canon) https://github.com/NewEraCracker/LOIC but the requests do not appear in my nginx logs and I feel no slowdown - Apache Jmeter https://jmeter.apache.org/ but I can't drop my infra and I have Java socket closed errors - K6 https://k6.io/ but I can't bring down my infra with - wrk https://github.com/wg/wrk no matter what parameter I put it doesn't make enough requests per second, I put the same parameters as on a tutorial and I don't get the same result...

I use tools like vegeta and wrk2 to answer those questions.

A module can be an executable and a library at the same time. For example, https://github.com/tsenart/vegeta

Some tools to investigate: * https://prometheus.io/ * https://github.com/tsenart/vegeta

No, not at all. You just need a tool like Vegeta.

vegeta v12.8.4

Oh, just saw this. You wrote your comment while I wrote mine. If you can enumerate specifically what you want to see, please submit it to our issue tracker: https://github.com/caddyserver/website

Generally we encourage examples in our community wiki though: https://caddy.community/c/wiki/13 -- much easier to maintain that way.

Yes, the docs have been updated at https://github.com/caddyserver/website but haven't been deployed yet. There is a new protocols option:

    protocols h1 h2

Could you be more specific about these complaints? What examples don't work? We can't work on improving the docs if we don't get specific and actionable feedback. The docs are found at https://github.com/caddyserver/website if you want to propose any changes.

Protip: you can click almost everything in code blocks in the docs. For example, if you click `[]`, it brings you right to the request matcher syntax section, which explains what you can fill in there.

It would be redundant to write on every page what you can use as a matcher. The Caddyfile reference docs assume you've read https://caddyserver.com/docs/caddyfile/concepts which walks you through how the Caddyfile is structured, and it'll give you the fundamentals you need to understand the rest of the docs (I think, anyway).

If you think we need more examples for a specific usecase, we can definitely include those. Feel free to propose some changes on https://github.com/caddyserver/website, we could always use the help!