Fortinet white logo
Fortinet white logo

Administration Guide

Starting an HTTPS RPS test

Starting an HTTPS RPS test

The HTTPS RPS test is the same as the HTTP RPS test, except that it uses HTTPS traffic, and does not have the Limit by option; also, the MTU is editable.

To start an HTTPS RPS test:
  1. In Performance testing, expand HTTPS and click RPS.
  2. Click Create New.
  3. Configure the network or select a network template. See Using network configuration templates for how to create a network template.
  4. Select a Certificate Group, if applicable.
  5. Click OK.
  6. Configure the test case options described below.
  7. Click Start to run the test case.

FortiTester saves the configuration automatically so you can run the test again later. You can also click Save to save the test case without running it.

Tip 1: You can copy an existing case and change its settings to create a new case. In the case list, click Clone to clone the configuration. Only the case name is different from the original case.

Tip 2: You can add or edit a comment when the test is running. This comment can be used to search for the test result in the Results page. This is useful especially when the test runs for a long time.

HTTPS RPS test case options

For details about the common options for HTTPS cases, see HTTPS test case common options.

Settings Guidelines

Load

Mode

Simuser: Simulated users. Simuser simulates a user processing through an actions list one at a time. It allows you to determine the maximum number of concurrent users your device, infrastructure, or system can handle.
Connections/second: This mode simulates TCP connections, each of them containing up to hundreds of transactions. It's useful to test how many concurrent connections can be handled by your device.

NOTE: If you want FortiTester to create connections as fast as possible, set Mode to Simuser.

For more information, see What is the difference between Connections per Second and Simulated Users?

Requests per Connection Number of HTTP requests per connection. The default is 0, which means as many as possible. The valid range is 0 to 50,000.

Starting an HTTPS RPS test

Starting an HTTPS RPS test

The HTTPS RPS test is the same as the HTTP RPS test, except that it uses HTTPS traffic, and does not have the Limit by option; also, the MTU is editable.

To start an HTTPS RPS test:
  1. In Performance testing, expand HTTPS and click RPS.
  2. Click Create New.
  3. Configure the network or select a network template. See Using network configuration templates for how to create a network template.
  4. Select a Certificate Group, if applicable.
  5. Click OK.
  6. Configure the test case options described below.
  7. Click Start to run the test case.

FortiTester saves the configuration automatically so you can run the test again later. You can also click Save to save the test case without running it.

Tip 1: You can copy an existing case and change its settings to create a new case. In the case list, click Clone to clone the configuration. Only the case name is different from the original case.

Tip 2: You can add or edit a comment when the test is running. This comment can be used to search for the test result in the Results page. This is useful especially when the test runs for a long time.

HTTPS RPS test case options

For details about the common options for HTTPS cases, see HTTPS test case common options.

Settings Guidelines

Load

Mode

Simuser: Simulated users. Simuser simulates a user processing through an actions list one at a time. It allows you to determine the maximum number of concurrent users your device, infrastructure, or system can handle.
Connections/second: This mode simulates TCP connections, each of them containing up to hundreds of transactions. It's useful to test how many concurrent connections can be handled by your device.

NOTE: If you want FortiTester to create connections as fast as possible, set Mode to Simuser.

For more information, see What is the difference between Connections per Second and Simulated Users?

Requests per Connection Number of HTTP requests per connection. The default is 0, which means as many as possible. The valid range is 0 to 50,000.