wrk VS loadtest

> My initial requirement was to send requests with unique parameters. To the best of my knowledge, no tool could do this.

wrk does this with lua. https://github.com/wg/wrk/blob/master/src/wrk.lua

Also even things like the venerable jmeter supported pulling parameters from a csv file.

We used wrk2, a fantastic tool to generate stable load on the server. Wrk2 improves on wrk and adds the ability to generate sustained load at a specific rate (-R parameter).

I am using a tool called wrk to make a bunch of requests to my website, and changing the concurrency of the requests drastically changes the result, with concurrency set to 1, I get 894 requests made in 10 seconds, and when I set concurrency to 10, I get 8549 requests. This linear scaling stops when increasing the concurrency more drastically (18805 requests for 100 and 19814 for 500 concurrency).

Im creating multithreaded async http server for learning purposes and i'm facing problem when benchmarking with wrk. I get socket read errors on every connection:

We use locust at work but I HIGHLY recommend wrk for a very robust yet simple load testing tool.

https://github.com/wg/wrk

And of course, this talk by Gil Tene is fantastic if you're interested in load testing stats https://www.youtube.com/watch?v=lJ8ydIuPFeU

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...

You could try to just blast it with wrk or bombardier. Can easily get around 50k requests on consumer machine.

Sure, first I did the load testing on the same machine. The same machine ran web servers, php-fpm and ab / wrk programs.

There are http benchmarking tools like wrk [0]. You don't need a ddos service for that.

[0] https://github.com/wg/wrk

cluster - npm link loadtest - npm link "os" is a nodejs core module

More details: I am learning about node.js clustering. I have 6 core AMD CPU. for testing the load I used loadtest package. Both tests where executed by node server.js

For benchmarking, I will use apache bench. We can also use loadtest which has similar functionality.

To load test our Node.js servers with and without clustering, we will use the Vegeta load testing tool. Other options can be the loadtest npm package or the Apache benchmark tool as well. I find Vegeta easier to install and use because it is a Go binary, and the precompiled executables are seamless to install and get started.

When I throw loadtest on it, I got this:

I used https://www.npmjs.com/package/loadtest but my computer does not go over 100 rps. Why is that? I have a pretty good gaming computer.