High load of MSE receiver

[AdithyanIlangovan]

.	Normal receiver	MSE receiver - old	MSE receiver - new
Video process	45%	90%	90%
Audio process	9%	35%	36%

• The above shows the load of the process, as seen by the top command, when running the different receivers.
• The top two process (which are assumed to video and audio ) in terms of load are specified here.
• We need to find way to reduce the load in MSE receiver.
• One idea is to increase the buffer delay before appending to the websocket, it is expected that increasing the delay should decrease the load

Update 1:

.	Normal receiver	MSE receiver - old	MSE receiver - new	MSE receiver - stripped with only web socket reception
Video process	45%	90%	90%	46%
Audio process	9%	35%	36%	34%

Update 2:

We are not entirely sure, whether two process correspond to audio and video process. They could as well be two threads running inside chrome. This has to be further investigated. But the inference from the above table is that the websocket reception does take a lot of load on the system. We need to figure out a way to reduce this load.

(Flute Sender) ----> (Receive packets chunked into the size of 1428) ----->(Store inside the circular buffer) ----->(Lib websocket read from the circular buffer) ---> (Forwarded to the websocket of the javascript)

The reason we need the circular buffer in between is because the lib websocket read is an ansychronous process. And reads whenever it is done with a packet, so we need something in between where it can take those data from.