-
Hi,
1. What version of the project are you using?
v6.1.1
2. What operating system and processor architecture are you using?
Windows 10 (I know, I know), x64
go version go1.7.3 windows/amd64
3…
-
I am currently running vegeta against one endpoint and would retroactively like to understand why some of the requests failed. As the url is the same for all of the requests and they only differ in th…
-
Update Vegeta 6.1.1
-
I've been thinking that performance _should_ be better- I expect it to be more in the 10K RPS range than the 1K RPS range for a fast machine.
The way that we read TCP sockets is slightly out of the n…
-
I am using vegeta to load test, and the use case is to POST request with headers. I pass "X_MESSAGE_ID" but it is received at server as "X_message_id"
I understand that underscores are not used in he…
-
Update Vegeta to 6.1.1
-
**Description**
I'm trying to run a service on Docker swarm mode and it just fails and there is no way to debug it. I can do a docker run just fine, just not docker service create
**Steps to rep…
nlsun updated
8 years ago
-
Is it possible to have multiple workers, each executing a list of URLs in succession? This is opposed to having multiple workers, each executing a URL in the list in parallel.
i.e.
http://server:por…
-
We have an app that has just one endpoint and there is a nonce (`TransactionId` below) that needs to be set differently for each request. I tried the following:
```
payload["TransactionId"] = uuid.Ne…
-
httpstat has a very simple to understand graphical command line report of which part of the requests too most. Perahps offer a similar report visualisation on vegeta as well?
https://github.com/reorx/…