Skip to content

Latest commit

 

History

History
68 lines (42 loc) · 2.33 KB

File metadata and controls

68 lines (42 loc) · 2.33 KB

Network Next


Modify route shader for test buyer

The test server belongs to a test buyer, and this test buyer has a "route shader" that describes when to accelerate clients.

Right now the route shader is set to always take network next - even if there is no acceleration found - for testing purposes.

Let's modify the route shader for the test buyer, so it only accelerates players if we can find at least 1 millisecond of latency reduction.

Open the file terraform/dev/relays/main.tf and make the following changes:

force next false

Commit the changes:

git commit -am "disable force next"
git push origin

Apply the changes with terraform:

cd ~/next/terraform/dev/relays
terraform init
terraform apply

The terraform actions have updated the route shader for the test buyer in the postgres database.

To make these changes live, we need to commit them to the dev environment:

cd ~/next
next database
next commit

This is the process for making any changes to the dev database configuration in terraform:

  1. Modify terraform files
  2. terraform init and apply
  3. Commit the database changes

Please wait a few minutes for the updated settings to take effect, they should be live in less than a minute.

Connect a test client again:

run client

You will see that now it probably won't be accelerated:

session not accelerated

Drilling in to the session you can now see only the non-accelerated latency, so the session is not accelerated.

session detail not accelerated

Obviously, it's not particularly impressive to see a session not be accelerated. We want to see some acceleration!

To make it easier to see real acceleration, let's move the test server to Sao Paulo, Brasil.

Up next: Move test server to Sao Paulo.