PREMISE:
I am implementing a client that communicates with the server using WebSocket. The kernel of the client application is built ontop LibGDX and it is deployed exclusively in the form of a browser using GWT (HTML5 / JavaScript). This is for a side project - a fast pace (high network traffic), an online browser game.
Without providing any source - essentially, the client code is an empty LibGDX application that provides the correct implementation of gwt-websockets (usually the recommended GWT wrapper for JavaScript websites).
SYMPTOMS OF THE PROBLEM:
(preliminary note: this seems to be a client-side issue). I launch the application and connect to the server. After 1000 ms, the client application sends the packet to the server and receives the packet back - no problem. There is also no problem sending and / or receiving two, three or even five packets per second.
Speeding up this process is faster, however ... approximately sending more than 10 packets per second (100 ms intervals) from the client to the server or receiving more than 10 packets per second (100 ms intervals) OR as sending and receiving 10 packets per second (100 ms intervals) ) cause the client to slowly fall into FPS when packets are poured, exited, or both. The larger the network connection, the lower the FPS floor becomes (it slowly flows from 60 ... 55..50..45 .. everything is down to 1 if you continue to send packets). Meanwhile, the server is completely healthy.
, , - - , ( : Websocket.onHandle() ), FPS ~ 60 . , , FPS ( , , ).
:
:
. , gwt-websockets , , .