Mega service scaling
This section introduces the scaling options, billing granularity, and common limitations of the Mega Block cloud positioning and mapping service, helping you plan resources and procurement strategies based on application scale and concurrency requirements.
The core of the Mega Block cloud positioning service is creating and purchasing a positioning service group, which is itself a service package, including standard and trial packages. The resources included in each package are as follows:
| Package item name | Standard | Trial |
|---|---|---|
| Mapping project tasks | 1 | 1 |
| Cloud positioning library count | 5 | 2 |
| Request concurrency QPS | 10 | 3 |
In the Mega Block mapping service, the core concepts and design principles are as follows:
- One location corresponds to one mapping project; each mapping project can be linked to a cloud positioning service group.
- Cloud positioning libraries within the same cloud service group share QPS quotas (billed per request, counted when carrying AppId and passing authentication).
- To support large-scale or complex scenarios, different floors or areas can be collected and mapped separately, and map fusion can be performed when needed.
Mega service scaling typically involves the following dimensions: concurrency QPS (Queries Per Second), cloud positioning library count, number of bound mapping projects, single-library map capacity, large-scale or complex scenario map fusion, and video input duration for a single mapping task. This section explains the meaning, impact, and scaling recommendations for each item.
Scalable items description
- Cloud positioning concurrent QPS
- Number of cloud positioning libraries sharing QPS
- Bound mapping projects
- Map capacity of each cloud positioning library
- Mapping capability expansion: input video duration, multi-map fusion
Cloud positioning service concurrent QPS
Concurrency statistics are based on QPS (queries per second), which refers to the number of service requests received by the server per second. As long as the request carries a valid cloud positioning library AppId and passes authentication, it will be counted in the concurrency statistics, regardless of whether the positioning is successful.
Concurrency is an attribute of the cloud service group, and all cloud positioning libraries within the same cloud service group share the QPS quota.
By default, after successful initialization, a device will send positioning requests at a frequency of once per second. Due to network latency and the randomness of request arrival times, it is theoretically possible for the actual instantaneous number of requests to exceed the quota. For example, a service group with 10 QPS can support approximately 10 devices running simultaneously. However, if more than 10 requests are received within a 1-second window for the same service group, the excess requests may be rejected.
To ensure service stability in multi-device concurrency scenarios, it is recommended to reserve some redundancy when purchasing QPS. For example, if you need to support 10 devices running stably, consider purchasing 11-12 QPS.
For management and scaling operations, refer to QPS scaling management operation guide.
Number of cloud positioning libraries
Cloud positioning library instances require cloud computing resources and are billed per instance, with each library corresponding to a unique AppId. Deleting and recreating a positioning library does not affect the quota, but the new library will generate a new AppId. If the default quota is insufficient, you can apply to increase the number of positioning libraries.
Note
Under normal circumstances, reopening a cloud positioning library and re-adding Mega Blocks will not affect positioning. However, after deactivating and reopening, the new positioning library's AppId will differ from the previous one.
To open cloud positioning libraries beyond the quota limit, refer to the document: Additional cloud positioning library operation guide
Bound mapping projects
The design philosophy of our product is that one location corresponds to one Mega Block mapping project, and one project corresponds to the activation of one cloud positioning service group.
If you need to associate more mapping projects with the same service group, please refer to the operation guide to ensure proper configuration of resources and permissions: operation help for binding more mapping projects
Map capacity of a single cloud localization library
The design concept of the cloud localization library product is that one cloud localization library's positioning result is a coordinate system, serving one application. A single cloud localization library has a maximum allowed Block (map) capacity limit. The capacity measurement uses CC (EasyAR's proprietary unit of measurement). After exceeding the limit, adding maps will be restricted. However, through resource deployment and capacity expansion, we still allow the addition of multiple maps. Each Mega Block has a capacity attribute, which is related to the size of the localizable area and resource usage.
| Each cloud localization library | Limit |
|---|---|
| Block capacity | 4500 CC |
The current default upper limit example is 4500 (subject to the actual product configuration). If higher capacity is needed, please contact sales or operation support: Map capacity expansion operation help
Mapping limitations and capacity expansion
Mega Block mapping requires computational resources and service costs. The cost is related to the area you need to map, the recognition zones, and the duration of the captured videos.
| Each mapping task | Limitations |
|---|---|
| Single captured video | 16 clips * 8 minutes/clip |
| Single project | 50,000 square meters |
For each task, the product has certain limitations on the duration of the input video for a single captured video. The video limit is 16 clips * 8 minutes/clip. A single map corresponds to a single captured video, while complex multi-maps can correspond to multiple captured videos.
A single project is limited to 50,000 square meters of mapping. For specific inquiries, please contact our sales team. Contact sales now
For complex scenarios or large-scale spaces requiring multiple map integrations, please consult sales for activation. Most positioning scenarios can be handled using multiple independent single maps without the need for map integration. It is recommended to consult sales before use to determine whether the multi-map integration feature needs to be activated.
For more detailed operational assistance, refer to the documentation: Mapping capacity expansion operational guide
Related topics: