Quotas and limits in Message Queue
Written by
Updated at April 28, 2025
Yandex Message Queue has the following limits:
- Quotas are organizational constraints that our support team can change upon request.
- Limits are technical constraints of the Yandex Cloud architecture. You cannot change the limits.
If you need more resources, you can increase your quotas in one of the following ways:
- Make a request to increase your quotas.
- Contact support, detailing which quotas you want increased and by how much.
To have your request processed, you must have the quota-manager.requestOperator role or higher, e.g.,editor or admin.
You can manage quotas using Cloud Quota Manager.
Quotas
Messages
| Type of limit | Value |
|---|---|
Number of SendMessage and SendMessageBatch calls per queue |
300 calls per second for a standard queue |
Number of ReceiveMessage calls per queue |
300 calls per second for a standard queue |
Number of DeleteMessage and DeleteMessageBatch calls per queue |
300 calls per second for a standard queue |
Number of ChangeMessageVisibility and ChangeMessageVisibilityBatch calls per queue |
300 calls per second for a standard queue |
Number of CreateQueue calls per cloud |
2 calls per second |
Number of DeleteQueue calls per cloud |
5 calls per second |
| Number of other request calls per cloud | 100 calls per second |
| Number of queues per cloud | 1,000 |
Limits
Queues
| Type of limit | Value |
|---|---|
Minimum message enqueue delay (DelaySeconds parameter) |
0 seconds |
Maximum message enqueue delay (DelaySeconds parameter) |
900 seconds (15 minutes) |
| Number of messages being processed per standard queue | 120,000 |
| Number of messages being processed per FIFO queue | 20,000 |
| Rate of enqueueing messages in a FIFO queue | 100 messages per second |
| Queue name | Maximum of 80 characters, including numbers, lowercase and uppercase Latin letters, hyphens, and underscores. The name of a FIFO queue must end with the .fifo suffix. |
Messages
| Type of limit | Value |
|---|---|
Number of SendMessage and SendMessageBatch calls per queue |
30 calls per second for a FIFO queue |
Number of ReceiveMessage calls per queue |
30 calls per second for a FIFO queue |
Number of DeleteMessage and DeleteMessageBatch calls per queue |
30 calls per second for a FIFO queue |
Number of ChangeMessageVisibility and ChangeMessageVisibilityBatch calls per queue |
30 calls per second for a FIFO queue |
| Batch entry ID | Maximum of 80 characters, including numbers, lowercase and uppercase Latin letters, hyphens, and underscores |
| Maximum number of message attributes | 10 |
| Maximum number of entries per batch | 10 |
| Message content | XML, JSON, and unformatted text. The following Unicode characters are supported:
|
| Maximum period for retaining messages in a queue | 1,209,600 seconds (14 days) |
| Minimum period for retaining messages in a queue | 60 seconds (1 minute) |
Maximum message enqueue delay (DelaySeconds parameter) |
900 seconds (15 minutes) |
Minimum message enqueue delay (DelaySeconds parameter) |
0 seconds |
| Maximum message size | 262,144 bytes (256 KB) |
| Minimum message size | 1 byte |
| Maximum message visibility timeout | 12 hours |
| Minimum message visibility timeout | 0 seconds |
Maximum client message wait time in an empty queue (WaitTimeSeconds parameter) |
20 seconds |