Desktop performance depends on the whole connection
Remote desktop performance is also affected by your local Wi-Fi, ISP routing, packet loss, image encoding, and resolution. The same node can feel different on different networks. Test with real editing, window switching, and timeline scrubbing rather than relying on a single latency reading.
Latency isn't the whole story for builds
Once your code is on the machine, compilation mainly uses the node's CPU, memory, and storage. Network conditions have a more direct effect on cloning code for the first time, downloading dependencies, uploading assets, and retrieving build artifacts. Track transfer time and build time separately when you test.
Run a real-world test first
Try a daily rental on the network you normally work from. Connect to the desktop, then upload a representative project or set of assets. If the display is unresponsive, check your local connection and routing before choosing a longer billing period.
Nodes operate normally 365 days a year. Get the actual connection address, port, and authentication details from the instance page in the console. Do not use information on this plan page as connection credentials.