volkswagen VS loadtest

Or, more practically, they may be using pytest-vw (https://github.com/auchenberg/volkswagen).

import volkswagen

#1: Please don’t use “win” as an abbreviation for Microsoft Windows in GNU software or documentation. [...] calling something a “win” is a form of praise. You’re free to praise Microsoft Windows on your own if you want, but please don’t do so in GNU packages. | 60 comments #2: 'volkswagen' detects when your tests are being run in a CI server and makes them pass | 19 comments #3: In 2001, I said "I use Linux" to RMS's face, and interrupted his usual rant by explaining that the userspace was not GNU, so I did mean "Linux". He was speechless for the best 5 seconds of my life. | 34 comments

So they need https://www.npmjs.com/package/volkswagen

Along with no tests, you should probably remove any linting tools. If the code doesn't still have to work maybe consider removing ci/cd, or just https://github.com/auchenberg/volkswagen

Best repo on GitHub.

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.