Skip to main content

How to send a request to your service many times and load it

Since app version 1.4.0

Pick a request in the inspector's log and click "Replay" → "N times…": it goes to the service as many times as you set, and the inspector shows how many answers came, how many failed and how fast the service answered. For a scenario of several requests, there is "Load" with a collection. Both work on the Pro and Ultra plans (what the inspector does for free).

The requests go straight to the service on your computer, past the log, and the service carries out every one: a handler that charges money, sends emails or writes to a database does it each time.

How to repeat a request N times​

  1. Open an HTTPS tunnel's "Requests" tab (how to open the inspector) and pick a row in the log.
  2. Click the arrow next to "Replay" and pick "N times…". The "Repeat N times" window opens.
  3. In "How many times", set 1 to 1000; in "How many at once", how many requests go out together, 1 to 20.
  4. Click "Start". While the requests go out, the button turns into "Stop".

A collection's request has the same: "⋯" → "Repeat N times". A new request can go many times at once: in the "New request" window, click the arrow on the "Send" button and pick "Send and repeat N times…".

How to load the service with a collection​

A collection is a set of requests saved from the log (how to build a collection).

  1. Open the collection in the "Collections" view and click "Load". The "Load with the collection" window opens.
  2. In "Users at once", set 1 to 20; in "Passes each", how many times each user goes through the whole collection. The total is at most 1000 sends: the window shows the number.
  3. Click "Start".

What the result shows​

  • "Sent", "Answered", "Failed" and "Per second".
  • "Answers by status": how many answers came with 2xx, 3xx, 4xx and 5xx codes.
  • "Failures" by kind, if there were any.
  • "Response time (answered only)": until the connection, until the first byte and in full, with the minimum, the median, the 90th, 95th and 99th percentiles and the maximum.
  • For a load run, also the result of each request of the collection.

Run it again with "Again", and the window compares the run with the previous one: failures, the median, the 95th percentile and requests per second. A run stops by itself after 10 minutes. If you close the window, the run goes on and the result comes as a notification.

Check​

When every request has gone out, the top of the window says "Done: all sends went out", and "Answered" equals "Sent" if the service answered each one.