loadtest 7.1.0 → 7.1.1

package/.github/FUNDING.yml

@@ -0,0 +1,13 @@
+# These are supported funding model platforms
+
+github: alexfernandez
+patreon: # Replace with a single Patreon username
+open_collective: # Replace with a single Open Collective username
+ko_fi: # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+otechie: # Replace with a single Otechie username
+lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry
+custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

package/README.md

@@ -85,14 +85,18 @@ so that you can abort deployment e.g. if 99% of the requests don't finish in 10
 but it is still limited.
 `loadtest` saturates a single CPU pretty quickly,
 so it uses half the available cores in your processor.
-If you see that the Node.js processes are above 100% usage in `top`,
-which happens approx. when your load is above 4000~5000 rps per core,
-please adjust the number of cores.
+The Node.js processes can reach 100% usage in `top`,
+which happens approx. when your load is above 4000~7000 rps per core.
+In this case please adjust the number of cores.
 So for instance with eight cores you can expect to get a maximum performance of
-8 * 5000 ~ 40 krps.
-(You can measure the practical limits of `loadtest` on your specific test machines by running it against a simple
+8 * 5000 = 40 krps.
+
+You can measure the practical limits of `loadtest` on your specific test machines by running it against a simple
 [test server](#test-server)
-and seeing when it reaches 100% CPU.)
+and seeing when it reaches 100% CPU. Run the following commands on two different consoles:
+
+    $ node bin/testserver.js
+    $ node bin/loadtest.js -n 1000000 -c 100 http://localhost:7357/
 
 If you have reached the limits of `loadtest` even after using all cores,
 there are other tools that you can try.
@@ -100,7 +104,7 @@ there are other tools that you can try.
 * [AutoCannon](https://www.npmjs.com/package/autocannon): also an `npm` package,
 awesome tool with an interface similar to `wrk`.
 * [Apache `ab`](http://httpd.apache.org/docs/2.2/programs/ab.html)
-has great performance, but it is also limited by a single CPU performance.
+has great performance, but it is limited by a single CPU performance.
 Its practical limit is somewhere around ~40 krps.
 * [weighttp](http://redmine.lighttpd.net/projects/weighttp/wiki) is also `ab`-compatible
 and is supposed to be very fast (the author has not personally used it).

package/lib/loadtest.js

@@ -108,7 +108,7 @@ class LoadTest {
 				this.stop();
 			}
 		}
-		if (this.running && !this.requestsPerSecond) {
+		if (this.running && !this.options.requestsPerSecond) {
 			next();
 		}
 		if (this.options.statusCallback) {

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "loadtest",
-	"version": "7.1.0",
+	"version": "7.1.1",
 	"type": "module",
 	"description": "Run load tests for your web application. Mostly ab-compatible interface, with an option to force requests per second. Includes an API for automated load testing.",
 	"homepage": "https://github.com/alexfernandez/loadtest",