This topic describes the limits of Real-Time Communication (RTC).
SDK limits for each platform
Platform | Limits |
Windows |
|
Mac |
|
iOS |
|
Android |
|
HarmonyOS |
|
Linux |
|
Web | Limits vary by platform and browser. For more information, see Browser compatibility and known issues. |
Concurrency limits
Type | Concurrency quota |
Concurrent channels per application | Unlimited. |
Concurrent users per channel | The default limit is 100 concurrent users per channel. To increase the limit, submit a ticket. |
Maximum subscriptions per client | The default limit is 17 subscriptions. To increase the limit, submit a ticket. |
Bypass stream ingest tasks | A maximum of 3 concurrent tasks per channel. To increase the limit, submit a ticket. |
Recording tasks | A maximum of 3 concurrent tasks per channel. To increase the limit, submit a ticket. |
Channel duration | The default duration is 24 hours. To shorten the duration, configure the "Token options" parameter. For more information, see Use token-based authentication. To extend the duration, submit a ticket. |
Number of applications | The default limit is 100. To increase the limit, submit a ticket. |
Custom layouts per application | The default limit is 100. To increase the limit, submit a ticket. |
Custom recording templates per application | The default limit is 100. To increase the limit, submit a ticket. |
Custom stream ingest templates per application | The default limit is 100. To increase the limit, submit a ticket. |
Other limits
Type | Limits |
Request rate for a single OpenAPI | 10 per second. If this limit does not meet your business requirements, submit a ticket. |
Data retention period |
|
Naming requirements for ChannelID and UserID |
|
Naming requirements for UserName | Must be UTF-8 encoded and no more than 64 bytes in length. |
Limits on the frequency and length of real-time messages from a single client |
|