mirror of
https://github.com/minio/minio.git
synced 2025-01-05 20:13:22 -05:00
a5702f978e
Additionally set - x-ratelimit-limit - x-ratelimit-remaining To indicate the request rates.
34 lines
1.5 KiB
Markdown
34 lines
1.5 KiB
Markdown
# MinIO Server Throttling Guide [](https://slack.min.io) [](https://hub.docker.com/r/minio/minio/)
|
|
|
|
MinIO 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 MinIO 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 MinIO cluster to be operationally resilient to such workloads, while also making sure the drives are at optimal efficiency and responsive.
|
|
|
|
Example: Limit a MinIO 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
|
|
minio server http://server{1...8}/mnt/hdd{1...16}
|
|
```
|
|
|
|
or
|
|
|
|
```sh
|
|
mc admin config set myminio/ api requests_max=1600
|
|
mc admin service restart myminio/
|
|
```
|
|
|
|
> NOTE: A zero value of `requests_max` means MinIO will automatically calculate requests based on available RAM size and that is the default behavior.
|
|
|