> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/inforiver-enterprise-on-prem/how-to-guides/scaling-redis-cache-legacy-service.md).
# Scaling Redis Cache (Legacy service)
### Steps for Redis Scaling
1. Select the Redis cache resource from the respective resource group.
2. In the left-side menu, click **Scale** under **Settings** menu. You can also search for **Scale** in the search bar and select it from the results displayed.
3. Under the Scale Configuration section, choose the desired configuration for your Redis cache:
Redis Scaling
**Cache Size:** Select the appropriate cache size based on your requirements. You can choose from various cache sizes ranging from Basic to Premium tiers.
**Replicas:** Specify the number of read replicas you want to have for high availability and improved performance. This option is available in the **Premium** tier.
4. Review the pricing details and estimated costs associated with the selected configuration.
5. Click on **Apply** button to initiate the scaling operation.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.inforiver.com/inforiver-enterprise-on-prem/how-to-guides/scaling-redis-cache-legacy-service.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
