Normally you don’t see it by eye, but the game actually is divided into 250ms intervals. This means it is the players fault for choosing a bad network or they live in an area with bad network conditions before the data reaches the fast google network.

THE ONLY LAG YOU EXPERIENCE IS CAUSED IN BETWEEN THE GOOGLE NETWORK. In summary: The more jumps you do through bad networks, the bigger the latency gets. It is designed to take as less hops as possible. The google network itself is optimized for low latency (latency = the time the data takes to get to the other players phone). Also it is undefined because you never know how many hop the data needs to take until it connects with the google network. This behavior of going from one network to another is called hop. It is almost certain that the data goes through other networks you don’t even know of before it reaches the stable google network. If you do a PvP fight the data you send goes from your network to the google network and then from there back to the other players network. In short: The GCP infrastructure is NOT the problem. It is also used by google itself for huge applications like youtube or gmail. This is a massive optimized IoT structure created by google. The server infrastructure is build with the google cloud platform (GCP). The game matchmaking is the only thing that happens on the server.

The p2p protocol establishes a direct connection from your phone to the other persons phone and is used because it is faster than most other network protocols. PvP uses a peer-to-peer (p2p) network protocol, so there is no server in between! In this post I try to give a brief introduction about the infrastructure and networking that is done in db legends. Everyday you can see posts about lag and connection issues, but most people don’t seem to have a understanding about what actually goes on behind the scenes.

Dragon ball legends game random closes