> For the complete documentation index, see [llms.txt](https://docs.caraml.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.caraml.dev/user-guides/router/create-a-router/configure-autoscaling.md).

# Configure autoscaling

You can also configure the amount of resources (CPU/Memory) allocated for each replica of your router as well as lower and upper limits for the autoscaling.

![](https://2689420226-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFMRO0BquZrbmgj6RBGJL%2Fuploads%2Fgit-blob-924ca9d3d78d61ad29e3827684a4d9d2ca84c79f%2Fcreate_router_resources.png?alt=media)

{% hint style="warning" %}
In most situations, 500m CPU and 0.5Gi memory should suffice, however, you can fine tune this configuration based on the data from Turing monitoring dashboard.
{% endhint %}

## Autoscaling Policy

By default, Turing uses request concurrency as a measure to monitor performance. For situations that require more fine-grained control, you can also choose a different autoscaling metric and adjust the target value according to prior load tests.

Currently, 4 metrics are supported - Concurrency, RPS, CPU and Memory.

![](https://2689420226-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFMRO0BquZrbmgj6RBGJL%2Fuploads%2Fgit-blob-5501cf8b1dbf0739674da64279955b6c00525a27%2Fautoscaling_policy_panel.png?alt=media)