> OctoPerf load testing - Strategy documentation page. How to configure the strategy of a User profile.

Source: https://api.octoperf.com/doc/runtime/edit-scenario/edit-user-profile/user-load/

# Load

This page lets you define the load profile associated with the select user profile.

A load profile is composed of a number of inflexion points each defined with:

- A time of occurrence,
- A number of concurrent users.

OctoPerf will increase or decrease the load during the test to reach each one of these points.

!!! warning
    If you have defined [alternate stopping conditions](https://api.octoperf.com/doc/analysis/test-status/#test-stopping-events), the real load may look different than the load profile.

!!! info
    For a [K6 Virtual User](https://api.octoperf.com/doc/design/create-virtual-user/import-k6-scripts/), this load replaces the `scenarios`, `vus`, `duration`, `iterations` and `stages` of the script `options`. [Import Scenario](https://api.octoperf.com/doc/design/create-virtual-user/import-k6-scripts/#import-the-scenario) fills in the load of each user profile from the K6 scenarios of the script.

## Load chart

Through the various inflexion points, it is possible to directly edit the curve. Note that actions taken here will also reflect in the [table below](#load-table):

![Add point](https://api.octoperf.com/doc/runtime/edit-scenario/edit-user-profile/img/add-remove-point.gif "Add point")

| Action                             | Description                     |
| ---------------------------------- | ------------------------------- |
| **Left-click** anywhere            | Create a new point              |
| **Left-click** on a point          | Select a point                  |
| **CTRL + Left-click** on a point   | Remove this point               |
| **Drag and drop** a selected point | Move the coordinates of a point |

!!! note
    You cannot drag a point before its predecessor or after its successor.

## Load table

You can use the table under the graph in order to [edit the curve](#load-chart) as well:

![Edit table](https://api.octoperf.com/doc/runtime/edit-scenario/edit-user-profile/img/edit-table.gif "Edit table")

| Action                                                | Description                                                  |
| ----------------------------------------------------- | ------------------------------------------------------------ |
| ![add-line](https://api.octoperf.com/doc/runtime/edit-scenario/edit-user-profile/img/add-line.png){ .off-glb } Add a new point      | Create a new point                                           |
| ![remove-line](https://api.octoperf.com/doc/runtime/edit-scenario/edit-user-profile/img/remove-line.png){ .off-glb } Remove a point | Remove this point                                            |
| **Left-click** on a line                              | Select this point                                            |
| **Time**                                              | Configure the time of this point on the X axis               |
| **Virtual users**                                     | Configure the number of concurrent virtual users of this point on the Y axis |

## Rescale

The **Rescale** button allows you to Rescale the load to a target value while preserving its inflexion points:

![rescale-user-load.png](https://api.octoperf.com/doc/runtime/edit-scenario/edit-user-profile/img/rescale-user-load.png)

On this screen, you can define a target number for **Virtual users** and **Duration**. 

When applied, we will increase the size of the load profile to match the new values, exactly like an image that you would enlarge or reduce.

## Reshape

![reshape-user-load.png](https://api.octoperf.com/doc/runtime/edit-scenario/edit-user-profile/img/reshape-user-load.png)

In this menu you can create a brand-new load profile from one of our presets. Please refer to the [User load policy documentation](https://api.octoperf.com/doc/runtime/edit-scenario/#user-load-policy) for detailed information.

## WebDriver UserLoad

![User Profile WebDriver](https://api.octoperf.com/doc/runtime/edit-scenario/edit-user-profile/img/user-profile-web-driver.png "User Profile WebDriver")

Real-browser simulation consumes a lot more resources than regular JMeter load tests and when several are executed in parallel the response times may be inaccurate. Since real browsers   execute a lot of scripts (usually in [JavaScript](https://en.wikipedia.org/wiki/JavaScript)) and are not meant to be run in parallel they will often compete for available [CPU](https://en.wikipedia.org/wiki/Central_processing_unit) thus increasing scripts execution times. 

That is why *Webdriver virtual users* have their **number of concurrent users limited to 1**.