# Intelligent Scaling

A feature to scale your component to the max number of instances to reduce the data processing lag automatically. This feature detects the need to scale up the components in case of higher data traffic.

{% hint style="info" %}
*<mark style="color:green;">Please Note:</mark>* *This feature is available both in Spark & Docker components. This feature will only work with the **real-time** as invocation type.*
{% endhint %}

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fuq3RSHHup7fjHYaspk7y%2Fuploads%2FkQKdB3As1wIfrQmdGJMq%2Fintellegent_scaling_AdobeExpress.mp4?alt=media&token=1a384a4a-6209-4780-bc4e-7193f8bc30d3>" %}
Intelligent Scaling as a part of the ClickHouse Writer
{% endembed %}

All components have option of Intelligent scaling which is ability of the system to dynamically adjust the scale or capacity of the reader component based on the current demand and available resources. It involves automatically optimizing the resources allocated to the component to ensure efficient and effective processing of tasks.&#x20;

{% hint style="info" %}
*<mark style="color:green;">Please Note:</mark>*&#x20;

* *If you have selected intelligent scaling option make sure to give enough resources to component so that it can auto-scale based on the load.*
* *Components will scale up if there is a lag of more than 60% and if the lag goes less than 10% component pods will automatically scale down. This lag percentage is configurable.*
  {% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bdb.ai/data-pipeline-2/components/intelligent-scaling.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.