Region Setting

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

![](https://docs.paraverse.cc/media/202504/7a9c17a3a0c94b29a79ba0791ef0595f7618.png)

After the rendering service is successfully started, the partition information will be automatically displayed in the region settings interface. You can choose the city to which the region belongs, as shown in the image below:

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

When not using RTT detection, the client will allocate it to the partition belonging to the city closest in distance based on a distance-priority allocation strategy. If you choose to enable RTT detection, distance detection will no longer be performed, and RTT region detection will be performed on the front-end overview screen. The system will default to selecting the partition with the lowest network latency and prioritize allocation to the region with the lowest latency. If the specified region's resources are full, the system will roll back the resources to the resource pool and allocate them to other available regions.

Please note that when the website uses the HTTPS protocol, network detection needs to use the WSS protocol. Each detection node needs to be configured with an SSL certificate and configured on the domain name, otherwise RTT detection operations will not be possible.

**Directed Partition Setting:**

You can choose to specify the directed partition to a specific workspace. When the application selects semi-active synchronization, the application can only synchronize to the directed partition in the selected workspace.

**How to set up directed partitions?**

To set up directed partitions, you need to modify the configuration file of the agent. Set the value of `pxy.host.region-type` to `1` and then restart the agent service. In this way, once the server successfully registers, it will automatically become a directed partition.