> OctoPerf load testing - Random Container Action documentation page. Random Container Actions plays a random child action on each iteration.

Source: https://api.octoperf.com/doc/design/edit-virtual-user/action-types/logic-actions/random-container-action/

# Random Container Action

![random-container](https://api.octoperf.com/doc/design/edit-virtual-user/action-types/logic-actions/img/random-container.png){ align=left }

The random container plays a random child action on each iteration.
If you want to use it to replay several different subsets of requests, it's best to use normal containers inside a random container.

<div style="clear:both"></div>

![random-container](https://api.octoperf.com/doc/design/edit-virtual-user/action-types/logic-actions/img/random-container-tree.png){ align=right }

**A common use case is when replaying different types of search** and you want to have a response time for each.
**If you just put everything in one container** and made the search dynamic, **you would only get one averaged response time** for all of them.
**Using containers within a random container you can get a response time for each** type of search.

For instance here we see the results of using a random container:

![Random container](https://api.octoperf.com/doc/design/edit-virtual-user/action-types/logic-actions/img/random-container-example.png "Random container")

Of course **the more hits you make, the closest to 33/33/33 the distribution will be**.