---
metadata:
  - name: generator
    content: Diplodoc Platform v5.52.0
alternate:
  - https://yandex.ru/routing/doc/en/vrp/request-processing-time.md
  - https://yandex.ru/routing/doc/kk/vrp/request-processing-time.md
  - https://yandex.ru/routing/doc/ru/vrp/request-processing-time.md
  - href: en/vrp/request-processing-time.md
    type: text/markdown
    title: Markdown version
  - href: llms.txt
    type: text/markdown
    title: llms.txt
title: RouteQ — planning algorithm — request processing time
---
> **Documentation Index:** Fetch the complete configuration index at https://yandex.ru/routing/doc/en/llms.txt


# Request processing time

How long it takes to complete the task depends on the number of orders in your request and the length of the interval during which routes are planned. Of the two tasks with an equal number of orders, the one where routes are planned within a single day will be resolved faster, while the one where routes span two or more days will be resolved slower.

The table below shows approximately how long it takes to solve a planning task.

| **Number of orders in the request** | **Estimated time for solving the task**	|
| ----- | -----	|
| Under 50 | Up to 1 minute	|
| 100 | 8–10 minutes |
| 500 | 12–15 minutes |
| 1000 | 25–28 minutes |
| 5000 | 45–55 minutes |

{% note info %}

Time in the table is indicated for `normal` [solution quality](https://yandex.ru/routing/doc/en/vrp/options-quality.md).

{% endnote %}

<!-- source: en/vrp/_includes/feedback.md -->
<a href="feedback">
  <span class="button">Contact support</span>
</a>


<!-- endsource: en/vrp/_includes/feedback.md -->