Regional detection

## Region Latency Detection:

The system can detect the latency information of different cluster nodes and automatically select the cluster node with the lowest latency.

## Setting Cluster Information:

In the manager, each rendering server can set the partition name and partition ID, as shown in the image below:

![](https://docs.paraverse.cc/media/202504/35cc0c9a13f54126ac5b0d4cc4f4ae154744.png)

## Setting Regional City Information:

After the rendering service starts, the partition information will automatically display in the regional settings interface. You can choose the city to which the region belongs, as shown in the image below:

![](https://docs.paraverse.cc/media/202504/0d8d39aa4cf54f699ca21ac75e326d768668.png)

## Allocation Rules:

- When RTT detection is not enabled, the client will allocate resources to the partition belonging to the city closest to itself based on a distance priority allocation strategy.

- When RTT detection is enabled, the system will no longer perform distance detection but will conduct RTT regional detection at the front end and automatically select the partition with the lowest network latency. The system prioritizes allocation to the region with the lowest latency. If the specified region's resources are full, the system will fallback to the resource pool and attempt to allocate resources in other regions.

Please note that when a website uses the HTTPS protocol, network detection needs to use the WSS protocol. Therefore, each detection node needs to be configured with an SSL certificate and ensure the domain is correctly configured; otherwise, RTT detection will not be possible.