Problems Analysis

---

Introduction

Users feedback that the streaming experience is not good, and the video is blurred or stuck, which may be caused by the network or terminal performance issues. The following document will introduce how to confirm the specific problems caused by the poor play-stream current experience through the Analytics Dashboard (AD).

1 Network Problems Caused by Publish-stream Users

The following is a step-by-step guide on how to confirm whether the pull-stream experience is poor due to publish-stream user network problems.

Step One

Enter the stream end-to-end page.

Step Two

View the delay and packet loss of the publish-stream end and several other play-stream ends: a sharp increase in the same time range.

Step Three

View the device performance on the publish-streaming side: CPU/memory is normal.

Step Four

Judging the frame rate of the publish-streaming side: the sending frame rate drops sharply and is lower than the collection frame rate.

Based on the above points, it can be basically concluded that it is caused by the network problem of the publish user, and the user needs to be guided to switch to another network.

2 Network Problems Caused by Stream-Playing Users

The following is a step-by-step guide on how to confirm whether the play-stream experience is poor due to play-stream user network problems.

Step One

Go to the room page.

Step Two

Compare the flow quality data of "abnormal users" and "other users in the room":

1. There are more lagging than other users;
2. The frame rate is lower than other users and the amplitude is obvious.

Step Three

Go to the user page.

Step Four

View user's playing: all flows have high end-to-end delay/packet loss.

Step Five

View the user's device performance: normal.

Based on the above points, it can be basically concluded that it is caused by the network problem of the play user, and the user needs to be guided to switch to another network.

3 Publish-stream User's Equipment Performance Issues

The following is a step-by-step guide on how to confirm whether the play-stream experience is poor due to performance issues of publish-stream user's devices.

Step One

Enter the stream end-to-end page.

Step Two

View the performance of publish-stream user's equipment: CPU/memory full load.

Step Three

View publish and play user acquisition frame rate: low/abnormal.

Based on the above points, it can be basically concluded that it is caused by performance problems of the publish-stream user's equipment, and the user needs to be guided to replace the equipment.