Without any code example, the problem most likely is that your websocket client is flooded with a fire hose coming from the server.
Most likely, you could adjust this by getting a websocket client poll for the next frame when it is ready to process it. The advantage of this is that you could stop polling for frames for asset X and start polling for frames from asset Y.
Of course, it is assumed that the problem is related to the client side ... if it downloads all the videos on your server, etc. and canโt โreleaseโ the video to switch to another, then this is different on the server.
However, this is not a good use case for websites ... they are great for small data packages ... is this just an experiment?
source share