# Silo Server Throttling Guide [![Docker Pulls](https://img.shields.io/docker/pulls/pgsty/silo.svg?maxAge=604800)](https://hub.docker.com/r/pgsty/silo/)

Silo server allows to throttle incoming requests:

- limit the number of active requests allowed across the cluster
- limit the wait duration for each request in the queue

These values are enabled using server's configuration or environment variables.

## Examples

### Configuring connection limit

If you have traditional spinning (hdd) drives, some applications with high concurrency might require Silo cluster to be tuned such that to avoid random I/O on the drives. The way to convert high concurrent I/O into a sequential I/O is by reducing the number of concurrent operations allowed per cluster. This allows Silo cluster to be operationally resilient to such workloads, while also making sure the drives are at optimal efficiency and responsive.

Example: Limit a Silo cluster to accept at max 1600 simultaneous S3 API requests across all nodes of the cluster.

```sh
export MINIO_API_REQUESTS_MAX=1600
export MINIO_ROOT_USER=your-access-key
export MINIO_ROOT_PASSWORD=your-secret-key
silo server http://server{1...8}/mnt/hdd{1...16}
```

or

```sh
mc admin config set mysilo/ api requests_max=1600
mc admin service restart mysilo/
```

> NOTE: A zero value of `requests_max` means Silo will automatically calculate requests based on available RAM size and that is the default behavior.