connect_a_client_to_the_test_server.md

Connect a client to the test server

There is a test server already running in the dev environment.

You can see this test server running in google cloud if you look at VMs:

First, make sure source is built locally:

cd ~/next
make

Now can connect a client to this test server like this:

run client

Wait a few seconds and you should see your client session live in the portal:

Don't be concerned if it takes a while for the session counts in the top/right to update. They update once per-minute, and this is an intentional feature to make the session counting tractible at high session counts (like 10-20M CCU).

Next, click on "Servers" in the nav menu, and you can see the test server now has one session:

Click on "Relays" in the nav menu, and you'll see which relays are carrying your session:

Click on "Sessions" in the nav menu then and then click on your client session in the session list, and you will see real-time statistics for your session:

The blue line is latency in milliseconds before acceleration, orange line is the conservative predicted latency after acceleration, and the green is the actual accelerated latency.

Don't be concerned if you see the accelerated latency is higher than the non-accelerated latency. By default the test client is configured to always go across network next, even if no acceleration is found.

We will fix this in the next step.

Up next: Modify route shader for test buyer.