Regional Detection and Latency-Based Routing

Regional detection allows LarkXR to automatically route clients to the cluster node with the lowest latency, improving the user experience across geographically distributed deployments.

## Setting Cluster Partition Information

In the rendering node manager, assign each rendering server a **partition name** and **partition ID**.

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

## Configuring Regional City Mapping

Once the rendering service starts, the partition information appears in the regional settings interface. Select the city corresponding to each partition to enable geographic-aware routing.

## Allocation Logic

| Scenario | Behavior |
|---|---|
| RTT detection disabled | Allocates to the partition closest to the client (distance priority). |
| RTT detection enabled | Performs real-time RTT measurement at the frontend and selects the partition with the lowest latency. Falls back to other regions if the selected one is full. |

> **Note:** When using HTTPS, RTT detection requires WSS. Detection nodes must have a valid SSL certificate and domain configured.