mirror of
https://github.com/minio/minio.git
synced 2025-11-07 12:52:58 -05:00
cleanup markdown docs across multiple files (#14296)
enable markdown-linter
This commit is contained in:
@@ -8,7 +8,9 @@ MinIO server allows to throttle incoming requests:
|
||||
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.
|
||||
@@ -30,6 +32,7 @@ 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.
|
||||
|
||||
### Configuring connection (wait) deadline
|
||||
|
||||
This value works in conjunction with max connection setting, setting this value allows for long waiting requests to quickly time out when there is no slot available to perform the request.
|
||||
|
||||
This will reduce the pileup of waiting requests when clients are not configured with timeouts. Default wait time is *10 seconds* if *MINIO_API_REQUESTS_MAX* is enabled. This may need to be tuned to your application needs.
|
||||
@@ -50,4 +53,3 @@ or
|
||||
mc admin config set myminio/ api requests_max=1600 requests_deadline=2m
|
||||
mc admin service restart myminio/
|
||||
```
|
||||
|
||||
|
||||
Reference in New Issue
Block a user