What do the stats in the mobile SDK testbed debug overlay mean?

QUESTION:

What are the stats in the testbed debug, and what do they indicate?

ANSWER:

Publisher Debug

  • Red5 Pro Version: This is the version number of the Red5 Pro framework.
  • Rate: Bitrate being sent, and the total data sent (rounded).
  • Pkts Sent: Total number of packets sent.
  • Pkts Dropped: Total number of packets dropped. An indicator of network issues or that your bitrate is exceeding your bandwidth.
  • Q Size: The current length video and audio frames being stored in queue. Another indicator of network issues or that your bitrate is exceeding your bandwidth.

Subscriber Debug

  • Red5 Pro Version: This is the version number of the Red5 Pro framework.
  • Rate: Bitrate being received, and the total data received (rounded).
  • Buffer Time: Indication of how large the buffer is growing for the subscriber.
  • Latency: Indication of how many seconds behind real time the stream is running. The closer to zero this is, the closer to real-time the stream is displaying (Note: this can sometimes be oddly large without any real effects. Currently, we're not certain why this is occasionally off).
  • Sub Q Size: The current length of video and audio frames being read into the queue. Larger numbers can sometimes indicate that the stream is either not being kept up with, or that there is a content issue.
  • Q Audio Frames: The number of audio packets that are received and parsed, but are waiting to be presented.
  • Q Video Frames: Same as above but with video.
  • Pkts Received: Total number of packets received.
  • A Pkts Dropped: Number of audio packets that have been dropped. Typically an indicator of network performance or signal issues.
  • V Pkts Dropped: Number of video packets that have been dropped. Typically an indicator of network performance or signal issues.
  • V Time2Decode: The time it took to decode the last video frame. We added this to debug so developers can easily see the impact of hardware acceleration in the examples. If this increases, the device CPU may be experiencing load or performance issues, or the content being decoded is intensive for the CPU.

 

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.