QPS estimation and scaling

Concurrency is measured in QPS (Queries per second), which represents the number of valid service requests received by the server per second. Regardless of whether the positioning is successful, as long as the request carries the correct cloud positioning library AppId and passes authentication, it will be counted in the concurrency statistics.

After successful initialization, devices will send positioning requests at a default frequency of once per second. Due to network latency and variations in request arrival times, instantaneous concurrency may exceed the QPS limit. For example, 10 QPS theoretically supports 10 devices, but if more than 10 requests are received within the same second, the excess requests will be rejected. To ensure service stability in multi-device concurrency scenarios, it is recommended to reserve some redundancy when purchasing QPS. For instance, when supporting 10 devices, you may configure 11–12 QPS.

The cloud positioning service group provides 10 concurrency by default, which meets the needs of most application scenarios. For higher-concurrency usage scenarios, we also offer flexible resource scaling solutions:

During high-concurrency periods such as holidays, you can choose short-term scaling packages to temporarily increase concurrency capacity
For applications with a large user base that require stable high-concurrency support, additional concurrency resources can be permanently bound to the cloud service group for its entire validity period

On top of the 10 QPS, you can flexibly choose short-term top-up packages or long-term fixed concurrency quota increases to adapt to resource requirements at different business stages.

Performance when concurrency exceeds the limit

When requests momentarily exceed the allocated QPS, the service will return the following error message (example):

statuCode: 21, message: "Exceed your QPS limitation"

Trial users who cannot locate may likely be due to insufficient QPS. It is recommended to check the response message by enabling logs through Mega Toolbox. As shown in the figure:

qps-limit

Note

Trial users have relatively small concurrency quotas. If they cannot locate, it is recommended to pay attention to whether there are error messages indicating exceeded limits.

Concurrency qps expansion

You can expand the concurrency quota through two approaches:

Offline consultation with business or customer service (suitable for large-scale, long-term, or customized needs)
Online direct upgrade in the management console (suitable for temporary or small-scale expansion)

Offline consultation for business upgrade

When the expected daily concurrency exceeds 50 QPS, it is recommended to contact EasyAR sales or customer service to arrange capacity expansion and resource guarantees. After scaling up, please log in to the developer backend to confirm whether the quota has taken effect.

The process for confirming the concurrency quota is shown in the box below:

Steps:

Developer Center -> Block Cloud Localization -> Cloud Localization Service Group -> Current QPS

check-qps

It is recommended to confirm the upgraded QPS quantity and validity period. Check through the EasyAR management interface, as described in the next section: Concurrency QPS Management

Online upgrade

The console provides two entry points for online QPS upgrades, as shown below:

Development Center -> Block Cloud Positioning -> Cloud Positioning Service Group -> Upgrade
Development Center -> Block Cloud Positioning -> Cloud Positioning Service Group -> QPS Details -> Upgrade

add-qps

Important

For high-concurrency requirements exceeding 50 QPS, please consult the business team to ensure stable resource supply.

Manage concurrent QPS

The main aspects of concurrency management include:

View the current number of QPS
Scale QPS
Extend the validity period of some QPS

Management interface

Steps

Upgrade QPS quantity and validity period

qps-manage

Enter the QPS details, the interface is as shown above. The current QPS quantity is displayed in the box marked on the right side of the image.

The timeline in the middle of the interface shows the validity period of the basic QPS part and the upgraded QPS part.

The purchase records at the bottom display the details of the upgrade orders and their validity periods.

Suggestions

Estimate the expected peak concurrency rather than the average concurrency, and reserve redundancy for the peak (e.g., for a peak of 10 QPS, it is recommended to purchase 11–12 QPS).
During holidays or events, short-term supplementary packages can be temporarily purchased to meet high-concurrency demands.
Post-expansion verification: use the Mega Toolbox in high-concurrency scenarios to confirm that requests are not rejected and responses remain stable.
If persistent rejections or anomalies occur, collect logs and contact the support team for troubleshooting (include the time window, the AppId of the cloud positioning library, and, if possible, provide a packet capture file containing request samples and error codes).

Table of Contents