Tag Info

Hot answers tagged

5

tl;dr You control how much data you are willing to process each frame. If a packet is too big, break it into smaller cells and process them one at a time (i.e one each frame). If you get a lot of small packets than split the group into chunks and limit the amount of information processing that is done each frame. The client does not need all the information; ...


1

You're worried that if you optimize something now, it might turn out to be wasted effort in the future. But more importantly, if your system is working now, as-is, then it's wasted effort here in the present! That said, minimizing server-client traffic is generally a good idea, especially if the clients are out in the real world, on unknown networks, and ...


1

There are two possible approaches to what you are describing, one wrong and the other useful. The wrong approach is to simply delay the user input from activating the command. Assuming you know the other clients can be informed 99.9% of the time in half a second, delay the command for half a second and send it to the other clients as the pair <command, ...


1

I assume that when your network data arrives, its processing diverts enough CPU power to slow down your rendering process. Are you enforcing a constant framerate or are you just rendering frames as fast as you can? Assuming you have a constant framerate, you may chose when your network packets are processed. I mean by that that your websocket event should ...



Only top voted, non community-wiki answers of a minimum length are eligible