- network:
variance in Round Trip Time or too low data rate so the internal data buffer runs "dry" and the browser needs to wait tilll it fills up again
- processing power:
cpu or gpu struggle to support the video decoding
when using hw accelerated graphics the cpu load should be low since the gpu takes over the processing
for activating HW acceleration for FF i wrote an artice:
https://forum.mxlinux.org/viewtopic.php ... 18#p697918
you could start a ping to a server IP (ideally to the streaming server but google.com will also do...) and let it run for 24h.
When you stop it (ctrl+c) you get a statistics like
Code: Select all
rtt min/avg/max/mdev = 30.538/72.832/405.100/94.690 ms
What you are interested in is the difference between min and max - that tells you the variance in the RTT.
Ideally min=max=avg
So this is an example for an suboptimal connection with min: 30.5ms and max: 405.1ms
This is a better one:
Code: Select all
rtt min/avg/max/mdev = 30.606/34.230/44.281/3.568 ms
I guess it's due to processes the CPU has to do for the network connection.
So testing with high CPU loads is also advisable - and if that's the case reducing the CPU load by having the GPU do the graphics processing