Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/cjus/requestmob
Network Request Mob - load generation tool
https://github.com/cjus/requestmob
Last synced: about 1 month ago
JSON representation
Network Request Mob - load generation tool
- Host: GitHub
- URL: https://github.com/cjus/requestmob
- Owner: cjus
- License: mit
- Created: 2018-03-15T19:23:01.000Z (almost 7 years ago)
- Default Branch: master
- Last Pushed: 2021-12-06T15:22:53.000Z (about 3 years ago)
- Last Synced: 2024-09-18T08:31:24.172Z (4 months ago)
- Language: JavaScript
- Size: 297 KB
- Stars: 0
- Watchers: 3
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Request Mob
The angry mob load generation tool
Request Mob is a load generation / testing tool. As a command line tool it will execute test scripts (called actors) on every CPU core on the machine it runs on.
A mob "actor" is a script which represents a particular type of network client. That client might be an HTTP or WebSocket client or both if you wish.
You execute request mob by first specfiying the duration of the test in seconds. The parameters that follow indicate the name of the actors you'd like to execute during the test duration.
For example, here we execute an actor call `hydra.health`:
```shell
$ node requestMob 10 hydra.health
```
## Other run options
You can install requestmob globally using:
```shell
$ npm install -g requestmob
```
Or you can run requestmob via a Docker container. Begin by building a docker image and pushing to your docker repo:
```shell
$ docker build --no-cache=true -t yourname/requestmob:0.1.5
```
Then create the following `requestmob` shell script which you can copy to /usr/bin/local or execute directly.
```shell
docker run --rm -it \
-v $(pwd)/actors:/usr/src/app/actors \
-v $(pwd)/config:/usr/src/app/config \
yourname/requestmob:0.1.5 "$@"
```
Make sure to update `yourname` and `0.1.5` version above.
In both cases make sure that the directory where you execute the requestmob command contains both a `config` directory (with a config.json file) and an `actors` subdirectory with your test scripts.
```
.
├── actors
│ ├── actor.js
│ ├── hmr.http.relay.js
│ ├── hmr.ws.relay.c100.d60.js
│ ├── hmr.ws.relay.js
│ └── hydra.health.js
└── config
└── config.json
```
## Building custom actors
An actor is a node script which sits inside of the actors subdirectory and which derives from the actor.js base class.
Each actor script requires a class with two functions: 1) constructor() 2) execute(). Actors also require a configuration entry in the config.json file.
```js
{
"hmr.http.relay": {
"description": "Call HMR HTTP relay endpoint",
"host": "localhost",
"port": 5353
},
"hmr.ws.relay": {
"description": "Call HMR websocket relay endpoint",
"wsTarget": "ws://localhost:5353"
},
"hmr.ws.relay.c100.d60": {
"description": "Call HMR websocket repay endpoint using 100 clients for 60 seconds",
"wsTarget": "ws://localhost:5353"
},
"hydra.health": {
"description": "Call Hydra Health endpoint",
"host": "localhost",
"port": 5353
}
}
```
A config entry consist of a named branch - using the name of the actor script (minus the .js extension) and an object containing a description and any other keys the actor requires.
## Actor runtime execution
While an actor is running it has access to a special property in its process environment.
```js
let workerID = process.env['WORKER_ID']);
```
The workerID is an index into a list of CPU cores. Each actor runs on a separate core and thus has a different workerID. This is useful when you need a unique base index to differentiate between concurrent execution of tests.