javascript – Multiplayer recreation – Participant place updates transmission sample

I am constructing a really primary 3D multiplayer recreation utilizing Three.js and Socket.io the place all of the participant does is transfer in an surroundings.

Contemplating there will likely be ~ 100 gamers in a single room and all information that’s required to be transmitted is their positions. Which of the next two patterns must be used :

1. Instantly echoing the participant’s place to different gamers within the room when a socket occasion is obtained :

Server aspect :

        socket.on("transfer", (singlePlayerPos) => {
           socket.to(socket.room).emit("participant replace", singlePlayerPos);
        });

Consumer aspect: receiving the occasion and updating the gamers place saved in an array/map.
Notice : consumer at present emits the place replace occasion on each body.

2. Storing the positions on server aspect and transmitting them on a ‘tick price’ foundation say each 16 ms

        setInterval(operate () {
            io.to(socket.room).emit("positions", allPlayersPositions);
        }, 16);

I am at present utilizing strategy #1 and have issues whether or not it will result in too many messages for consumer to deal with because the place occasion is emitted throughout each requestAnimationFrames() cycle.

The problem I’ve with strategy #2 is that my servers are horizontally scaled and utilizing L4 load balancing (there is not any sticky session). The sockets are scaled utilizing Redis adapter (pub/sub) so I am unable to actually retailer participant’s positions in reminiscence (RAM) as participant belonging to a single room can be a part of totally different servers. If I will need to retailer all positions they’re going to need to be saved in Redis which i am involved would affect efficiency (latency).
Moreover the consumer is fairly mild weight on the “recreation logic” half however have many different conventional internet parts (equivalent to modals, buttons and many others.) on the enterprise logic half … so do not actually intend to introduce complexity equivalent to interpolations and predictions (its okay if some gamers lag/skip at full load).

I am a newbie in the case of recreation improvement and would recognize any options and/or criticism.