Rel - Pure Elixir, publicly available TURN server

Rel is publicly available for tests and experiments. Just execute a simple POST request to obtain your credentials and copy-paste them into RTCPeerConnection constructor.

$ curl -X POST "https://turn.bigcow.ovh/?service=turn&username=johnsmith"
{
    "password":"l6hs9SzUgudFeb5XjrfCfOWKeOQ=",
    "ttl":1728,
    "uris":["turn:167.235.241.140:3478?transport=udp"],
    "username":"1691574817:johnsmith"
}

pc = new RTCPeerConnection({
  iceServers: [
    {
      credential: "l6hs9SzUgudFeb5XjrfCfOWKeOQ=",
      urls: "turn:167.235.241.140:3478?transport=udp", 
      username: "1691574817:johnsmith" 
    }
  ]
});

Benchmarks

We have N connections, where every connection consists of one client and one peer. A client creates an allocation, a peer starts sending data through this allocation to the client and the client echo back this data to the peer.

Questions we wanted to answer:

1. How many such connections are we able to handle?
2. How big bitrates are we able to handle?
3. What is the impact of datagram payload size on the TURN server performance?

Testbed

• Rel version: 0.2.0
• coTURN version: 4.5.2
• eturnal version: 1.11.1
• TURN server machine: AMD EPYC 7502P 32-Core Processor
• Clients and Peers machine: AMD EPYC 7502P 32-Core Processor
• RAM: 126 GB
• Connection link: 10 Gbbps

Results

Notes:

• ? means that eturnal was not able to create more than 1000 connections
• crashes means that eturnal was not able to read incoming data fast enough, which resulted in a packet loss. This doesn’t mean that the CPU usage was high.